Vehicle to everything application messaging

ABSTRACT

A user device and transportation entity, such as a transport vehicle or transport server, perform information exchanges for a transportation service using Device-to-Device (D2D) communications, such as dedicated short-range communication (DSRC), a cellular Vehicle-to-Everything (C-V2X), or a 5G New Radio (NR). The information exchanges, for example, are related to, e.g., logistics and delivery of transportation services. For example, the user device may transmit a transportation request message that includes information elements, such as an identifier, a type of transport device requested, a number of users, requested destination, etc. The transportation entity may transmit a transportation response message accepting or rejecting the request. Additional messages, such as a status request and status of the transportation, as well as messages related to completing the transportation service may be exchanged.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a Continuation of U.S. application Ser. No.17/124,003, entitled “VEHICLE TO EVERYTHING APPLICATION MESSAGING” andfiled on Dec. 16, 2020, which claims the benefit of and priority to U.S.Provisional Application No. 62/961,154, filed Jan. 14, 2020, andentitled “VEHICLE TO EVERYTHING APPLICATION MESSAGING,” all of which areassigned to the assignee hereof and is incorporated herein by referencein their entireties.

BACKGROUND Background Field

The subject matter disclosed herein relates to wireless communicationssystems, and more particularly to methods and apparatuses for vehicle toeverything (V2X) message exchange in a wireless communications system.

Relevant Background

Vehicular communication systems are areas of active interest in thecommunications industry for providing information useful intransportation. Vehicular communication systems, for example, includenodes, such as roadside units (RSUs) and the vehicles themselves, thatwirelessly transmit traffic related information and is being developedas part of intelligent transportation systems (ITS). For example,vehicular communication systems include direct communication systems,such as dedicated short-range communication (DSRC), cellularVehicle-to-Everything (C-V2X) communication, and even 5G New Radio (NR)communications.

The traffic related information to be communicated in currentlycontemplated vehicular communication systems is related to safetyapplications. For example, message exchanges currently contemplated invehicular communication systems are directed to aspects such as safetywarnings, traffic congestions (e.g., automated traffic control), andcoordinated or automated vehicle maneuvering.

SUMMARY

A user device and transportation entity, such as a transport vehicle ortransport server, perform information exchanges for a transportationservice using Device-to-Device (D2D) communications, such as dedicatedshort-range communication (DSRC), a cellular Vehicle-to-Everything(C-V2X), or a 5G New Radio (NR). The information exchanges, for example,are related to, e.g., logistics and delivery of transportation services.For example, the user device may transmit a transportation requestmessage that includes information elements, such as an identifier, atype of transport device requested, a number of users, requesteddestination, etc. The transportation entity may transmit atransportation response message accepting or rejecting the request.Additional messages, such as a status request and status of thetransportation, as well as messages related to completing thetransportation service may be exchanged.

In one implementation, a method of performing information exchange for atransportation service by a user device, includes transmitting atransportation request message to a transportation entity wirelessly,the transportation request message comprises one or more messageinformation elements including an identifier for the user device, and arequested destination; receiving a transportation response message fromthe transportation entity wirelessly, the transportation responsemessage comprises one or more message information elements includingacceptance or rejection of the transportation request message; andtransmitting a transportation confirm message to the transportationentity wirelessly in response to the acceptance in the transportationresponse message, the transportation confirm message comprises one ormore message information elements including the identifier for the userdevice.

In one implementation, a user device configured to perform informationexchange for a transportation service, the user device includes awireless transceiver configured to communicate with a transportationentity wirelessly; at least one memory; and at least one processorcoupled to the wireless transceiver and the at least one memory, the atleast one processor configured to: transmit a transportation requestmessage to the transportation entity, via the wireless transceiver, thetransportation request message comprises one or more message informationelements including an identifier for the user device, and a requesteddestination; receive a transportation response message from thetransportation entity, via the wireless transceiver, the transportationresponse message comprises one or more message information elementsincluding acceptance or rejection of the transportation request message;and transmit a transportation confirm message to the transportationentity, via the wireless transceiver, in response to the acceptance inthe transportation response message, the transportation confirm messagecomprises one or more message information elements including theidentifier for the user device.

In one implementation, a user device configured to perform informationexchange for a transportation service, includes means for transmitting atransportation request message to a transportation entity wirelessly,the transportation request message comprises one or more messageinformation elements including an identifier for the user device, and arequested destination; means for receiving a transportation responsemessage from the transportation entity wirelessly, the transportationresponse message comprises one or more message information elementsincluding acceptance or rejection of the transportation request message;and means for transmitting a transportation confirm message to thetransportation entity wirelessly in response to the acceptance in thetransportation response message, the transportation confirm messagecomprises one or more message information elements including theidentifier for the user device.

In one implementation, a non-transitory storage medium including programcode stored thereon, the program code is operable to configure at leastone processor in a user device to perform information exchange for atransportation service, includes program code to transmit atransportation request message to a transportation entity wirelessly,the transportation request message comprises one or more messageinformation elements including an identifier for the user device, and arequested destination; program code to receive a transportation responsemessage from the transportation entity wirelessly, the transportationresponse message comprises one or more message information elementsincluding acceptance or rejection of the transportation request message;and program code to transmit a transportation confirm message to thetransportation entity wirelessly in response to the acceptance in thetransportation response message, the transportation confirm messagecomprises one or more message information elements including theidentifier for the user device.

In one implementation, a method of performing information exchange for atransportation service by a transportation entity, the method includesreceiving a transportation request message from a user devicewirelessly, the transportation request message comprises one or moremessage information elements including an identifier for the userdevice, and a requested destination; transmitting a transportationresponse message to the user device wirelessly, the transportationresponse message comprises one or more message information elementsincluding an acceptance or rejection of the transportation requestmessage; and receiving a transportation confirm message from the userdevice wirelessly in response to an acceptance in the transportationresponse message, the transportation confirm message comprises one ormore message information elements including the identifier for the userdevice.

In one implementation, a transportation entity configured to performinformation exchange for a transportation service, the transportationentity includes a wireless transceiver configured to communicate with auser device; at least one memory; and at least one processor coupled tothe wireless transceiver and the at least one memory, the at least oneprocessor configured to: receive a transportation request message fromthe user device, via the wireless transceiver, the transportationrequest message comprises one or more message information elementsincluding an identifier for the user device, and a requesteddestination; transmit a transportation response message to the userdevice, via the wireless transceiver, the transportation responsemessage comprises one or more message information elements including anacceptance or rejection of the transportation request message; andreceive a transportation confirm message from the user device, via thewireless transceiver, in response to an acceptance in the transportationresponse message, the transportation confirm message comprises one ormore message information elements including the identifier for the userdevice.

In one implementation, a transportation entity configured to performinformation exchange for a transportation service, the transportationentity includes means for receiving a transportation request messagefrom a user device wirelessly, the transportation request messagecomprises one or more message information elements including anidentifier for the user device, and a requested destination; means fortransmitting a transportation response message to the user devicewirelessly, the transportation response message comprises one or moremessage information elements including an acceptance or rejection of thetransportation request message; and means for receiving a transportationconfirm message from the user device wirelessly in response to anacceptance in the transportation response message, the transportationconfirm message comprises one or more message information elementsincluding the identifier for the user device.

In one implementation, a non-transitory storage medium including programcode stored thereon, the program code is operable to configure at leastone processor in a transportation entity to perform information exchangefor a transportation service, the non-transitory storage mediumincluding includes program code to receive a transportation requestmessage from a user device wirelessly, the transportation requestmessage comprises one or more message information elements including anidentifier for the user device, and a requested destination; programcode to transmit a transportation response message to the user devicewirelessly, the transportation response message comprises one or moremessage information elements including an acceptance or rejection of thetransportation request message; and program code to receive atransportation confirm message from the user device wirelessly inresponse to an acceptance in the transportation response message, thetransportation confirm message comprises one or more message informationelements including the identifier for the user device.

BRIEF DESCRIPTION OF THE DRAWING

Non-limiting and non-exhaustive aspects are described with reference tothe following figures, wherein like reference numerals refer to likeparts throughout the various figures unless otherwise specified.

FIG. 1 illustrates a wireless communication system in which a userdevice is in wireless communications with a transportation entity.

FIG. 2 illustrates another wireless communication system in which a userdevice is in wireless communications with transportation entities.

FIG. 3 is a signal flow illustrating an example of message exchangebetween a user device and one or more transportation entities, such as atransport vehicle and/or transport server, for transportation serviceoperations.

FIG. 4 is a signal flow illustrating another example of message exchangebetween a user device and one or more transportation entities, such as atransport vehicle and/or transport server, for transportation serviceoperations.

FIG. 5 is a flow chart illustrating a method of performing informationexchange for a transportation service by a user device.

FIG. 6 is a flow chart illustrating a method of performing informationexchange for a transportation service by a transportation entity.

FIG. 7 shows a schematic block diagram illustrating certain exemplaryfeatures of a user device configured to perform an information exchangefor a transportation service with a transportation entity.

FIG. 8 shows a schematic block diagram illustrating certain exemplaryfeatures of a schematic block diagram illustrating certain exemplaryfeatures of a transportation entity configured to perform an informationexchange for a transportation service with a user device.

DETAILED DESCRIPTION

Vehicular communication systems, such as Vehicle to Everything (V2X),may be used, for example, for safety related applications, such assafety warnings, traffic congestions (e.g., automated traffic control),and coordinated or automated vehicle maneuvering. Application layermessages and information elements (IEs) to support safety relatedapplications are being defined by various standards developmentorganizations. For example, Society of Automotive Engineers (SAE) ispreparing work item J3186 Maneuver Sharing and Coordinating Service andJ2945/6 Performance Requirements for Cooperative Adaptive Cruise Controland Platooning. In China, Baidu has initiated a Phase 3 messagedefinition effort for coordinated driving. Such messages areprerequisites for intelligent transportation systems (ITS), for example,for coordinated or automated vehicle maneuvering and traffic control.

As discussed herein, vehicular communication systems additionally may beused for non-safety applications. Non-safety applications may solvenumerous use case issues, for example, for transport vehicles (e.g.,train, bus, rideshare, etc.) and user device interactions with transportvehicles (e.g., logistics, delivery, etc.). Vehicular communicationsystems, e.g., direct wireless communications between V2X entities, maybe used to engage (e.g., request, confirm, obtain status, etc.)transportation for a consumer or a service. For example, a user, e.g., aconsumer, may use vehicular communication systems to request orotherwise communicate with a transport vehicle or transport service tobe used as transportation for the user. In another example, a user,e.g., an entity or service, may use vehicular communication systems torequest or otherwise communicate with a transport vehicle or transportservice to be used as delivery transportation for goods or services,such as freight, food delivery, etc.

In one implementation, a set of application-layer IEs delineatetransport vehicle and user device interactions, such as transportationrequests or registration, status, and transportation completion orderegistration. Transportation related messages may be, e.g., dedicatedmessages in Device-to-Device (D2D) communication link, such as dedicatedshort-range communication (DSRC), cellular Vehicle-to-Everything (C-V2X)communication, 5G New Radio (NR) communication such as 5G NR-basedsidelink communication, or similar wireless communication systems.

FIG. 1 illustrates a V2X wireless communication system 100 in which V2Xservices operate using direct wireless communications between the V2Xentities. As illustrated, a user device 102 associated with user 104 maydirectly communicate with various other entities wirelessly, such as atransportation entity, shown as a transport vehicle 110 (illustrated asa bus) via a Vehicle-to-Pedestrian (V2P) communication link 111 or aroad side unit (RSU) 120 via a Vehicle-to-Infrastructure (V2I)communication link 121. FIG. 1 illustrates the user 104 as a person whomay be a consumer of the transportation, e.g., user 104 may betransported by the transport vehicle 110. In some implementations,however, the user 104 may be an entity, such as a restaurant, store,etc., and the transport vehicle 110 may be used to transport goods orservices provided or requested by the user 104.

A roadside unit (RSU) is a stationary infrastructure entity supportingV2X applications that can exchange messages with other entitiessupporting V2X applications. The user device 102 may be in wirelesscommunication with the transport vehicle 110 via the RSU 120, via V2Pcommunication link 121 and V2I communication link 123. The wirelesscommunication, for example, may be over, e.g., Proximity-based Services(ProSe) Direction Communication (PC5) reference point as defined by the3rd Generation Partnership Project (3GPP) body of standards, such as inTechnical Specification (TS) 23.303, and may use wireless communicationsunder IEEE 1609, Wireless Access in Vehicular Environments (WAVE),Intelligent Transport Systems (ITS), dedicated short rangecommunications (DSRC), cellular Vehicle-to-Everything (C-V2X), and IEEE802.11p, on the ITS band of 5.9 GHz, or other wireless connectionsdirectly between entities. During direct communications with one or moreentities in the V2X wireless communication system 100, each entityprovides V2X information, such as an identifier for the V2X entity, aswell as other information in messages such as Common Awareness Messages(CAM) and Decentralized Notification Messages (DENM) or Basic SafetyMessage (BSM), which may be used for, e.g., Advanced Driver AssistanceSystem (ADAS) or safety use cases, such as lane changes, speed changes,overtaking speeds, etc. As discussed, herein, the user device 102 andthe transportation entity, e.g., transport vehicle 110, may furtherexchange messages related to transport vehicle and user deviceinteractions, such as logistics, delivery, status, etc.

FIG. 2 illustrates a Vehicle-to-Network (V2N) wireless communicationsystem 200 in which V2X services operate using a wireless networkbetween entities, such as Wireless Wide Area Networks (WWAN). Forexample, entities may communicate via the Long Term Evolution (LTE)network, where the radio interface between the user equipment (UE) andthe eNodeB is referred to as LTE-Uu, or other appropriate wirelessnetworks, such as “3G,” “4G,” or “5G” networks. As illustrated, the userdevice 102 may wirelessly communicate with a transportation entity, suchas the transport vehicle 110 or a transport server 220, through thenetwork infrastructure 210, which for the sake of example, will bereferred to as a LTE network, but may be a 5G NR network or other typeof network. As illustrated, the user device 102 may wirelesslycommunicate with the network infrastructure 210, e.g., a base station202, referred to as an eNodeB in the LTE network infrastructure 210 (ora gNodeB in a 5G NR network infrastructure), via a Uu interface 203. Asillustrated, in some implementations, the user device 102 may directlycommunicate with an RSU 230 via communication link 231, which interfaceswith a base station 204 via a Uu interface 205.

The base station 202 may communicate with other base stations, e.g.,base station 212 through the IP layer 214 and network 216, such as anEvolved Multimedia Broadcast Multicast Services (eMBMS)/Single CellPoint To Multipoint (SC-PTM) network. The transport server 220 may bepart of or connected to the IP layer 214, as illustrated, or may beexternal to the IP layer 214 and the network infrastructure 210. Thetransport server 220 may receive and route information between the userdevice 102 and the transport vehicle 110, as well as receive otherexternal inputs. The base station 212 may wirelessly communicate withthe transport vehicle 110 directly or through other V2X entities, suchas RSU 232 via Uu interfaces 213 or 215 and 233, respectively. The V2Ncommunication using the “Uu” interface may be used to exchange messagesusing, e.g., C-V2X, 5G NR communications, etc. The information exchangemay be similar to that discussed above, including messages related totransport vehicle and user device interactions, such as logistics,delivery, status, etc., but the information exchange is over a greaterdistance than the direct communications shown in FIG. 1 .

FIG. 3 is a signal flow 300 illustrating an example of message exchangebetween a user device 102, which may be used by an end user or otherentity, such as a restaurant, store, service, etc., and one or moretransportation entities, e.g., a transport vehicle 110 and/or transportserver 220, for transportation service operations. The transportationservices, for example, may be related to public transport, such as citybuses, trolleybuses, trams (or light rail) and passenger trains, rapidtransit (metro/subway/underground, etc.), ferries, airlines, coaches,and intercity rail. Transportation services may further includeparatransit, vehicles for hire (e.g., taxicabs, rickshaws, limousines,party buses etc.), scooter sharing, bicycle sharing, etc. Additionally,the transportation services may be used for delivery transport, e.g.,for freight, food, goods, or services. For example, the transportationservices may be used by an entity that provides goods or services to anend user (e.g., at the request of the end user). For example, an entity,such as a restaurant, store, delivery service, etc., may request atransport vehicle (delivery device) using a vehicular communicationsystem to deliver goods or services. The entity may be agnostic to thedelivery device, but instead may focus on cost and delivery time orother criteria specific to that requestor. In some implementations, arequest may be made by an end user and provided to the entity, e.g., arestaurant, store, delivery service, and the entity may request atransport vehicle (delivery device) using a vehicular communicationsystem. The messages may be dedicated messages or encapsulated in thedata payload, e.g., in a D2D communication link, such as C-V2X, DSRC,and/or 5G NR communications, such as 5G NR-based sidelinkcommunications.

At stage 1 of FIG. 3 , the user device 102 may transmit a transportregistration message to the transportation entity, e.g., transportvehicle 110. The transport registration message, for example, may betransmitted directly to the transport vehicle 110. In someimplementations, as illustrated by the dotted line, the transportationregistration may be transmitted to the transport server 220. Thetransport registration message, for example, may include an identifierfor the user device 102 and an identifier for the transport vehicle. Thetransport registration message, e.g., may include a payment method to becharged for transport. The transport registration message may be arequest for or registration with a transport specific or OriginalEquipment Manufacturer (OEM) specific. For example, if registering foror requesting a bus, the transportation registration message mayindicate the type of bus being requested, e.g., such as a city bus or across-country bus. Similarly, if registering for or requesting a train,the transportation registration message may indicate the type of trainbeing requested, e.g., a tram, a local train, or national train. Thetransportation registration message may provide a registration serveraddress for purchasing tickets or validating transportation pass (e.g.,bus pass). The transportation registration message may provideinformation such as ticket information or destination information. Thetransportation registration message may include requests for specialseating or luggage arrangements (such as bicycle storage), or requestsfor assistance, such as assistance with entering/exiting the transportvehicle, assistance with luggage, etc. The transportation registrationmessage may provide message specific information, such as a validationperiod for the transportation registration message. If the transport isrequested for delivery of goods or services, the transportationregistration message may provide information related to the goods orservices, e.g., identification, type, special requirements (e.g.,temperature control), as well as other information such as destination,cost and delivery time.

At stage 2, the transport vehicle 110 may send a validate registrationmessage to the transport server 220, e.g., if the user device 102 sentthe transportation registration message to the transport vehicle 110.The validate registration message may be used by the transport vehicle110 to validate the registration of the user device 102 with thetransport vehicle 110, e.g., to confirm that the user device 102 haspurchased a ticket or has a valid account for the transportationrequest, or, alternatively, to initiate the registration of the userdevice with the transportation vehicle or service.

At stage 3, the transport server 220 may send an acknowledgement for thetransportation registration message to the transport vehicle 110 or theuser device 102, e.g., if the message from stage 1 was transmitted tothe transport server 220.

At stage 4, the transport vehicle 110 may send an acknowledgement forthe transportation registration message to the user device 102.

The acknowledgement message from stage 3 and/or stage 4, e.g., mayprovide information such as an indication to the user device 102 wherethere are available seats or assigned seats, an indication of theestimated time to a user specific stop and/or next stop, routeinformation, or certification information, e.g., so that encryptedinformation broadcast by the transport vehicle 110 may be decrypted bythe user device 102.

At stage 5, the user device 102 and the transport vehicle 110 mayexchange transport specific information. The transport specificinformation may be exchanged directly, e.g., upon request, or may bebroadcast, e.g., upon request or periodically broadcast. In someimplementations, the transport specific information, whether sentdirectly to user device 102 or broadcast, may be encrypted, and the userdevice 102 may decrypt the messages using certification informationreceived, e.g., in an acknowledgement message from stages 3 and/or 4.The transport specific information may be case specific, by way ofexample, for a bus or train the transport specific information mayinclude route information, upcoming stops, or a periodic indication ofthe current location. Other examples of transport specific informationmay include available battery, available range, or potential parkingareas within a specific area for an electric scooter or bicycle, orinclude a route, location or stop information for ride sharingapplications. In the transport specific information, the user mayrequest updates, such as a status update, or an update to an itinerary,such as a change in destination, or a pass renewal, etc.

At stage 6, the user device 102 may send a deregistration (complete)message to the transport vehicle 110, or as indicated by the dottedline, to the transport server 220. The deregistration message may beused, for example, to indicate that the user would like to exit at aparticular stop or an upcoming stop. The deregistration message may alsobe used to compete a purchase at a destination, e.g., by charging thepayment method provided during registration based on user device's ride.

At stage 7, the transport vehicle 110 may send a deregistration(complete) message to the transport server 220, e.g., if the user device102 sent the deregistration message to the transport vehicle 110.

At stages 8 and 9, acknowledgment messages for the deregistrationmessage may be sent to the transport vehicle 110 and/or the user device10. The transport vehicle 110 or the transport server, for example, mayrequest as part of the deregistration process that the user device 102provide periodic signals to the transport vehicle 110, with which thetransport vehicle 110 or the transport server 220 may validate that theuser device 102 has exited the transport vehicle 110 at the appropriatestop, e.g., based on a change in the signal strength as the user device102 exits the transport vehicle 110 and the transport vehicle 110departs and the distance between the user device 102 and the transportvehicle 110 increases.

FIG. 4 is a signal flow 400 illustrating another example of messageexchange between a user device 102 and a transportation entity, whichmay be, e.g., transport vehicle 110 and/or transport server 220. Themessages exchanged may be dedicated messages or encapsulated (e.g., viaa Radio Resource Control (RRC) message or similar messages).

At stage 1 of FIG. 4 , the user device 102 may transmit a transportationrequest message to the transportation entity 110/220. The transportationrequest message may be issued by a user 104 (shown in FIGS. 1 and 2 )through the user device 102 to request transportation. Thetransportation request message may include particulars for thetransportation, such as a user device identifier (e.g., an octet randomidentifier to identify the requestor and ensure anonymity), thetransportation type requested (e.g., bus, train, subway, rideshare,etc.), the destination (e.g., selected from a map or address), number ofusers (e.g., number in user's party), user type (e.g., pedestrian,cyclist, scooter, wheelchair, stroller, other), validity or expirationof transportation request (e.g., providing an indication of how long theuser is willing to wait), a maximum the user is will to pay,identification of goods or services to be transported, specialrequirements (e.g., temperature control), etc. Table 1, by way ofexample, illustrates data fields, data elements, and contents thereofthat all or some of which may be included in a transportation requestmessage. Additionally, Table 1 provides suggestions of which data fieldsor data elements may be considered mandatory (M) or optional (O) in atransportation request message.

TABLE 1 Data Field (DF) Data Data Element Element Contents Mandatory/(DE) (DE) (DF, DE) Optional TemporaryID 4 octet random DE_TemporaryID::= M device identifier OCTET STRING to identify (SIZE(4)) requestor andensure anonymity Public- bus, train, May include: M Transportation-subway, DE_VehicleType (bus, Type rideshare, other passenger car)(user-entered) DE_BasicVehicleClass (ExpressBus, LocalBus, SchoolBus,Ambulance) Numberof- Integer count DE_Count Count ::= M RequestingUsers(user-entered) INTEGER (0 .32) RequestingUser- pedestrian,DF_RequestorType: M Type cyclist, scooter, otherTraveler- wheelchair,Pedestrian, stroller, other otherTraveler- Æ Number ofVisually-Disabled, instances = otherTraveler- Number ofPhysically-Disabled, RequestingUsers otherTraveler-Bicycle User/riderUser-entered DE_Latitude M destination destination. DE_Longitude •User-specified by selection on map • User-specified by address entry •Application converts to (latitude, longitude) Willingness Yes/NoWillingToShare ::= O to share (This DE could BOOLEAN be displayedconditionally to the user depending on type of public transit requested)Validity time/ Duration in DE_Duration M Expiration for hours, minutesrequest (indicate how long requester willing to wait) Maximum Date, TimeDF_DDateTime M travel time or (Lets back-end must destination serverarrival time recommend specific transportation type, and/or inform riderthe type chosen will not work) Maximum fare (This DE could Currency Owilling to pay be displayed conditionally to the user depending on typeof public transit requested) Requested- This could be for ODepartureTime delayed requests or trips that are planned in the futureBeacon- This could be Distance Threshold O Proximity- used for TimeThreshold Threshold rideshare applications of when the vehicle or usershould start initiating a sidelink beacon.

At stage 2 of FIG. 4 , the transportation entity 110/220 may transmit atransportation response message to the user device 102. Thetransportation response message may be transmitted from the transportvehicle 110 or from a central service, e.g., transport server 220, toaccept or reject the transportation request message transmitted in stage1. In some implementations, the transportation response message may befrom the transport server 220 and may be encapsulated (e.g., via RRCmessage and provided to the transport vehicle 110 for the transportvehicle 110 to make a determination of whether to accept or reject thetransportation request. The transportation response message may includeinformation, such as the transportation response type (e.g., accept orreject), transportation type, transportation identifier, fare, shared,estimated time of arrival (ETA) to pick up, and ETA to destination.Table 2, by way of example, illustrates data fields, data elements, andcontents thereof that all or some of which may be included in atransportation response message. Additionally, Table 2 providessuggestions of which data fields or data elements may be consideredmandatory (M) or optional (O) in a transportation response message.

TABLE 2 Data Field (DF) Data Element Contents Mandatory/ Data Element(DE) (DE) (DF, DE) Optional ResponseType Bit mapped to DE_ResponseType::= M values: ENUMERATED { • Accept Accept (0), • Reject Reject (1), •Status Status (2), } -- Encoded as 3-bit value Transportation- bus,train, May include: O Type rideshare, other DE_VehicleType (bus,passenger car) DE_BasicVehicleClass (ExpressBus, LocalBus, SchoolBus,Ambulance) Transportation- License plate, DF_TransportIdentity: OIdentity Bus number, DE_LicensePlate ::= Train Number OCTET STRING(SIZE(4)) Optional DE_BusNumber ::= OCTET STRING (SIZE(4)) OptionalDE_TrainNumber ::= OCTET STRING (SIZE(4)) Optional Fare Toll/FareCurrency O Shared/Individual Optionally Shared ::= BOOLEAN O includeddepending on transport type (e.g., ride-share vs. bus/train) ETA_PickupTime until DF_Duration O pickup ETA_Destination Estimated timeDF_DDateTime O of arrival to destination

At stage 3 of FIG. 4 , the user device 102 may transmit a transportationconfirm message to the transportation entity 110/220. The transportationconfirm message may be issued by a user 104 (shown in FIGS. 1 and 2 )through the user device 102 to accept the offered transportation, suchas the fare, etc. Table 3, by way of example, illustrates data fields,data elements, and contents thereof that all or some of which may beincluded in a transportation confirm message. Additionally, Table 3provides suggestions of which data fields or data elements may beconsidered mandatory (M) or optional (O) in a transportation confirmmessage.

TABLE 3 Data Field (DF) Data Data Element Element Contents Mandatory/(DE) (DE) (DF, DE) Optional TemporaryID 4 octet random DE_TemporaryID Mdevice identifier to ::= OCTET identify requestor STRING and ensure(SIZE(4)) anonymity User/rider User-entered DE_Latitude M destinationdestination. DE_Longitude • User-specified by selection on map •User-specified by address entry • Application converts to (latitude,longitude) ETA_Pickup Time until pickup DF_Duration M

At stage 4 of FIG. 4 , the transportation entity 110/220 may transmit atransportation confirm acknowledgment message to the user device 102.The transportation confirm acknowledgement message may be used toacknowledge the transportation confirmation and to, e.g., confirm pickup ETA, travel ETA, fare, etc.

At stage 5 of FIG. 4 , the user device 102 may transmit a transportationstatus request message to the transportation entity 110/220. Thetransportation status request message may include the user deviceidentifier and may request the status of transportation service, such asthe information related to a current location (such as a current stop,time to next stops, etc.) or information related to an estimate ofarrival to the requested destination, such as an ETA to destination,number of stops to destination, etc. Table 4, by way of example,illustrates data fields, data elements, and contents thereof that all orsome of which may be included in a transportation status requestmessage. Additionally, Table 4 provides suggestions of which data fieldsor data elements may be considered mandatory (M) or optional (O) in atransportation status request message.

TABLE 4 Data Field (DF) Data Data Element Element Contents Mandatory/(DE) (DE) (DF, DE) Optional TemporaryID 4 octet random DE_TemporaryID Mdevice identifier to ::= OCTET identify requestor STRING and ensure(SIZE(4)) anonymity User/rider User-entered DE_Latitude M destinationdestination. DE_Longitude • User-specified by selection on map •User-specified by address entry • Application converts to (latitude,longitude)

At stage 6 of FIG. 4 , the transportation entity 110/220 may transmit atransportation status message to the user device 102 in response to thetransportation status request message. The transportation statusmessage, for example, may be used to indicate the requested status ofthe transportation service, e.g., information related to a currentlocation, or information related to an estimate of arrival to therequested destination, such as ETA to destination, number of stops todestination, etc. In some implementations, the user device 102 maydetermine an estimate of arrival to the requested destination based oninformation related to the current location provided in the statusmessage. For example, the status message may provide the current stopfor a bus and the time between upcoming stops. The user device 102 maydetermine, based on the requested destination and known route and thestatus message, the time to the destination or number of stops to thedestination. It should be understood that multiple transportation statusrequest and transportation status messages may be exchanged between theuser device 102 and the transportation entity 110/220. Table 5, by wayof example, illustrates data fields, data elements, and contents thereofthat all or some of which may be included in a transportation statusmessage. Additionally, Table 5 provides suggestions of which data fieldsor data elements may be considered mandatory (M) or optional (O) in atransportation status message.

TABLE 5 Data Field (DF) Data Data Element Element Contents Mandatory/(DE) (DE) (DF, DE) Optional ETA_ • Estimated time of DF_DDateTime MDestination arrival to DE_Count Count destination ::= INTEGER •Estimated (0 . . . 32) number of stops to destination DestinationPhysical address DE_Latitude O Location mapped to latitude DE_Longitudeand longitude

At stage 7 of FIG. 4 , the user device 102 may transmit a transportationcomplete request message to the transportation entity 110/220. Thetransportation complete request message may request that the user device102 be permitted to disembark from the transport vehicle 110, e.g., atthe next stop, and that the transportation services terminate. Table 6,by way of example, illustrates data fields, data elements, and contentsthereof that all or some of which may be included in a transportationcomplete request message. Additionally, Table 6 provides suggestions ofwhich data fields or data elements may be considered mandatory (M) oroptional (O) in a transportation complete request message.

TABLE 6 Data Field (DF) Data Data Element Element Contents Mandatory/(DE) (DE) (DF, DE) Optional TemporaryID 4 octet random DE_TemporaryID Mdevice identifier to ::= OCTET identify requestor STRING and ensure(SIZE(4)) anonymity DisembarkRequest DE_Disembark Disembark ::= MBOOLEAN

At stage 8 of FIG. 4 , the transportation entity 110/220 may transmit atransportation complete request acknowledgment message to the userdevice 102 in response to and to acknowledge the transportation completerequest message. Table 7, by way of example, illustrates data fields,data elements, and contents thereof that all or some of which may beincluded in a transportation complete request acknowledgment message.Additionally, Table 7 provides suggestions of which data fields or dataelements may be considered mandatory (M) or optional (O) in atransportation complete request acknowledgment message.

TABLE 7 Data Field (DF) Data Data Element Element Contents Mandatory/(DE) (DE) (DF, DE) Optional ETA_Destination • Estimated time ofDF_DDateTime M arrival to DE_Count Count destination ::= INTEGER •Estimated number (0 . . . 32) of stops to destination DisembarkRequestDE_Disembark Disembark ::= M BOOLEAN

At stage 9 of FIG. 4 , the transportation entity 110/220 may transmit atransportation complete response message to the user device 102 inresponse to the transportation complete request message. Thetransportation complete response message may, e.g., confirm the routetaken, fare charged, etc. Table 8, by way of example, illustrates datafields, data elements, and contents thereof that all or some of whichmay be included in a transportation complete response message.Additionally, Table 8 provides suggestions of which data fields or dataelements may be considered mandatory (M) or optional (O) in atransportation complete response message.

TABLE 8 Data Field (DF) Data Data Element Element Contents Mandatory/(DE) (DE) (DF, DE) Optional TemporaryID 4 octet random DE_TemporaryID Mdevice identifier to ::= OCTET identify requestor STRING and ensure(SIZE(4)) anonymity Rider Ingress Rider ingress DE_Latitude M Locationlocation DE_Longitude Rider Egress Rider egress DE_Latitude M(disembark) location DE_Longitude Location Fare Toll/Fare Currency M

FIG. 5 is a flow chart illustrating a method of performing informationexchange for a transportation service by a user device, such as userdevice 102. As illustrated in block 502, the user device transmits atransportation request message to a transportation entity wirelessly,the transportation request message comprises one or more messageinformation elements including an identifier for the user device and arequested destination, e.g., as discussed at stage 1 of FIG. 3 or stage1 of FIG. 4 . By way of example, the transportation entity may be atransport vehicle 110, a transport server 220, or both. At block 504, atransportation response message is received from the transportationentity wirelessly, the transportation response message comprises one ormore message information elements including acceptance or rejection ofthe transportation request message, e.g., as discussed at stage 3 or 4of FIG. 3 or stage 2 of FIG. 4 . At block 506, a transportation confirmmessage is transported to the transportation entity wirelessly inresponse to the acceptance in the transportation response message, thetransportation confirm message comprises one or more message informationelements including the identifier for the user device, e.g., asdiscussed at stage 3 of FIG. 4 .

In one implementation, the transportation request message, thetransportation response message, and the transportation confirm messageare dedicated messages in a Device-to-Device (D2D) communication link,comprising one or more of a dedicated short-range communication (DSRC),a cellular Vehicle-to-Everything (C-V2X) communication, or a 5G NewRadio (NR) communication.

In one implementation, the transportation request message, thetransportation response message, and the transportation confirm messageare encapsulated in data payloads in a Device-to-Device (D2D)communication link, comprising one or more of a dedicated short-rangecommunication (DSRC), a cellular Vehicle-to-Everything (C-V2X)communication, or a 5G New Radio (NR) communication.

In one implementation, the one or more message information elements inthe transportation request message further comprise at least one of atype of transport device requested, a number of users, a validity timefor the transportation request message, a maximum travel time orrequired destination arrival time, or a combination thereof.

In one implementation, the one or more message information elements inthe transportation request message further comprise at least one of auser type, a willingness to share transport vehicle, a maximum fare, arequested departure time, a beacon proximity threshold, or a combinationthereof.

In one implementation, the one or more message information elements inthe transportation response message further comprise at least one of atransportation type, a transportation identifier, a fare, an indicationof whether the transportation is shared or individual, an estimated timeof arrival for pickup and an estimated time of arrival to destination,or a combination thereof.

In one implementation, the one or more message information elements inthe transportation confirm message further comprise at least one of therequested destination and estimated time of arrival for pickup, or acombination thereof.

In one implementation, the user device may further transmit atransportation status request message to the transportation entitywirelessly, the transportation status request message comprises one ormore message information elements including a query for informationrelated to a current location, e.g., as discussed at stage 5 of FIG. 3or stage 5 of FIG. 4 . The user device may further receive atransportation status message from the transportation entity wirelessly,the transportation status message comprises one or more messageinformation elements including information related to the currentlocation, e.g., as discussed at stage 5 of FIG. 3 or stage 6 of FIG. 4 .The user device may be further configured to determine an estimate ofarrival to the requested destination using the information related tothe current location.

In one implementation, the user device may further transmit atransportation status request message to the transportation entitywirelessly, the transportation status request message comprises one ormore message information elements including the identifier for the userdevice, a query for information related to an estimate of arrival to therequested destination, e.g., as discussed at stage 5 of FIG. 3 or stage5 of FIG. 4 . The user device may further receive a transportationstatus message from the transportation entity wirelessly, thetransportation status message comprises one or more message informationelements including the estimate of arrival to destination, e.g., asdiscussed at stage 5 of FIG. 3 or stage 6 of FIG. 4 . For example, theestimate of arrival to destination comprises one or more of estimatedtime of arrival to destination and estimated number of stops todestination. In another example, the one or more message informationelements in the transportation status message further includes adestination of the transport vehicle nearest the requested destination.

In one implementation, the user device may transmit a transportationcomplete request message to the transportation entity wirelessly, thetransportation status request message comprises one or more messageinformation elements including the identifier for the user device, and arequest to disembark, e.g., as discussed at stage 6 of FIG. 3 or stage 7of FIG. 4 . The user device may further receive a transportationcomplete acknowledgement message from the transportation entitywirelessly, the transportation complete acknowledgement messagecomprises one or more message information elements including an estimateof arrival to destination and a confirmation of the request todisembark, e.g., as discussed at stage 8 or stage 9 of FIG. 3 or stage 8of FIG. 4 . The user device may further receive a transportationcomplete response message from the transportation entity wirelessly, thetransportation complete response message comprises one or more messageinformation elements including the identifier for the user device, aningress location, and an egress location. In one example, thetransportation complete response message further comprises one or moremessage information elements including at least one of a fare and arequest to provide periodic signals to validate that the user device hasexited the transport vehicle.

FIG. 6 is a flow chart illustrating a method of performing informationexchange for a transportation service by a transportation entity,wherein the transportation entity may comprise, e.g., a transportvehicle 110, a transport server 220, or both. As illustrated in block602, the transportation entity receives a transportation request messagefrom a user device wirelessly, the transportation request messagecomprises one or more message information elements including anidentifier for the user device and a requested destination, e.g., asdiscussed at stage 1 of FIG. 3 or stage 1 of FIG. 4 . At block 604, atransportation response message is transmitted to the user devicewirelessly, the transportation response message comprises one or moremessage information elements including acceptance or rejection of thetransportation request message, e.g., as discussed at stage 3 or 4 ofFIG. 3 or stage 2 of FIG. 4 . At block 606, a transportation confirmmessage is received from the user device wirelessly in response to theacceptance in the transportation response message, the transportationconfirm message comprises one or more message information elementsincluding the identifier for the user device, e.g., as discussed atstage 3 of FIG. 4 .

In one implementation, the transportation request message, thetransportation response message, and the transportation confirm messageare dedicated messages in a Device-to-Device (D2D) communication link,comprising one or more of a dedicated short-range communication (DSRC),a cellular Vehicle-to-Everything (C-V2X) communication, or a 5G NewRadio (NR) communication.

In one implementation, the transportation request message, thetransportation response message, and the transportation confirm messageare encapsulated in data payloads in a Device-to-Device (D2D)communication link, comprising one or more of a dedicated short-rangecommunication (DSRC), a cellular Vehicle-to-Everything (C-V2X)communication, or a 5G New Radio (NR) communication.

In one implementation, the one or more message information elements inthe transportation request message further comprise at least one of atype of transport device requested, a number of users, a validity timefor the transportation request message, a maximum travel time orrequired destination arrival time, or a combination thereof.

In one implementation, the one or more message information elements inthe transportation request message further comprise at least one of auser type, a willingness to share transport vehicle, a maximum fare, arequested departure time, a beacon proximity threshold, or a combinationthereof.

In one implementation, the one or more message information elements inthe transportation response message further comprise at least one of atransportation type, a transportation identifier, a fare, an indicationof whether the transportation is shared or individual, an estimated timeof arrival for pickup and an estimated time of arrival to destination,or a combination thereof.

In one implementation, the one or more message information elements inthe transportation confirm message further comprise at least one of therequested destination and estimated time of arrival for pickup, or acombination thereof.

In one implementation, the transportation entity may further receive atransportation status request message from the user device wirelessly,the transportation status request message comprises one or more messageinformation elements including a query for information related to acurrent location, e.g., as discussed at stage 5 of FIG. 3 or stage 5 ofFIG. 4 . The transportation entity may further transmit a transportationstatus message to the user device wirelessly, the transportation statusmessage comprises one or more message information elements includinginformation related to the current location, e.g., as discussed at stage5 of FIG. 3 or stage 6 of FIG. 4 .

In one implementation, the transportation entity may further receive atransportation status request message from the user device wirelessly,the transportation status request message comprises one or more messageinformation elements including the identifier for the user device, aquery information related to an estimate of arrival to the requesteddestination, e.g., as discussed at stage 5 of FIG. 3 or stage 5 of FIG.4 . The transportation entity may further transmit a transportationstatus message to the user device wirelessly, the transportation statusmessage comprises one or more message information elements including theestimate of arrival to destination, e.g., as discussed at stage 5 ofFIG. 3 or stage 6 of FIG. 4 . For example, the estimate of arrival todestination comprises one or more of estimated time of arrival todestination and estimated number of stops to destination. In anotherexample, the one or more message information elements in thetransportation status message further includes a destination of thetransport vehicle nearest the requested destination.

In one implementation, the transportation entity may further receive atransportation complete request message from the user device wirelessly,the transportation status request message comprises one or more messageinformation elements including the identifier for the user device, and arequest to disembark, e.g., as discussed at stage 6 of FIG. 3 or stage 7of FIG. 4 . The transportation entity may further transmit atransportation complete acknowledgement message to the user devicewirelessly, the transportation complete acknowledgement messagecomprises one or more message information elements including an estimateof arrival to destination and a confirmation of the request todisembark, e.g., as discussed at stage 8 or stage 9 of FIG. 3 or stage 8of FIG. 4 . The transportation entity may further transmit atransportation complete response message to the user device wirelessly,the transportation complete response message comprises one or moremessage information elements including the identifier for the userdevice, an ingress location, and an egress location, e.g., as discussedat stage 8 or stage 9 of FIG. 3 or stage 9 of FIG. 4 . In one example,the transportation complete response message further comprises one ormore message information elements including at least one of a fare and arequest to provide periodic signals to validate that the user device hasexited the transport vehicle.

FIG. 7 shows a schematic block diagram illustrating certain exemplaryfeatures of a user device 700, which may be, e.g., user device 102 shownin FIGS. 1-3 , which is configured to perform an information exchangefor a transportation service with a transportation entity, which may bea transport vehicle 110, a transport server 220, or both. The userdevice 700 may, for example, include one or more processors 702, memory704, a Wireless Wide Area Network (WWAN) transceiver 710, and a WirelessLocal Area Network (WLAN) transceiver 740, which may be operativelycoupled with one or more connections 706 (e.g., buses, lines, fibers,links, etc.) to non-transitory computer readable medium 720 and memory704. The user device 700 may further include additional items, which arenot shown, such as a user interface that may include e.g., a display, akeypad or other input device, such as virtual keypad on the display,through which a user may interface with the user device, or a satellitepositioning system receiver. In certain example implementations, all orpart of user device 700 may take the form of a chipset, and/or the like.Transceiver 710 may be, e.g., a cellular transceiver, and may beconfigured to transmit and receive inter-vehicle communications, asillustrated in FIGS. 1 and 2 . The transceiver 710 may include atransmitter 712 enabled to transmit one or more signals over one or moretypes of wireless communication links and a receiver 714 to receive oneor more signals transmitted over the one or more types of wirelesscommunication links. Transceiver 740 may be, e.g., a short rangetransceiver, and may be configured to transmit and receive inter-vehiclecommunications wirelessly, as illustrated in FIGS. 1 and 2 . Thetransceiver 740 may include a transmitter 742 enabled to transmit one ormore signals over one or more types of wireless communication links anda receiver 744 to receive one or more signals transmitted over the oneor more types of wireless communication links. The transceivers 710 and740 enable the user device 700 to communicate with transportationentities using D2D communication links, such as DSRC, C-V2X, or 5G NR.

In some embodiments, user device 700 may include antenna 711, which maybe internal or external. The antenna 711 may be used to transmit and/orreceive signals processed by transceiver 710 and/or transceiver 740. Insome embodiments, user device antenna 711 may be coupled to transceiver710 and/or transceiver 740. In some embodiments, measurements of signalsreceived (transmitted) by user device 700 may be performed at the pointof connection of the user device antenna 711 and transceiver 710 and/ortransceiver 740. For example, the measurement point of reference forreceived (transmitted) RF signal measurements may be an input (output)terminal of the receivers 714, 744 (transmitters 712, 742) and an output(input) terminal of the user device antenna 711. In a user device 700with multiple user device antennas 711 or antenna arrays, the antennaconnector may be viewed as a virtual point representing the aggregateoutput (input) of multiple user device antennas.

The one or more processors 702 may be implemented using a combination ofhardware, firmware, and software. For example, the one or moreprocessors 702 may be configured to perform the functions discussedherein by implementing one or more instructions or program code 708 on anon-transitory computer readable medium, such as medium 720 and/ormemory 704. In some embodiments, the one or more processors 702 mayrepresent one or more circuits configurable to perform at least aportion of a data signal computing procedure or process related to theoperation of user device 700.

The medium 720 and/or memory 704 may store instructions or program code708 that contain executable code or software instructions that whenexecuted by the one or more processors 702 cause the one or moreprocessors 702 to operate as a special purpose computer programmed toperform the techniques disclosed herein. As illustrated in user device700, the medium 720 and/or memory 704 may include one or more componentsor modules that may be implemented by the one or more processors 702 toperform the methodologies described herein. While the components ormodules are illustrated as software in medium 720 that is executable bythe one or more processors 702, it should be understood that thecomponents or modules may be stored in memory 704 or may be dedicatedhardware either in the one or more processors 702 or off the processors.

A number of software modules and data tables may reside in the medium720 and/or memory 704 and be utilized by the one or more processors 702in order to manage both communications and the functionality describedherein. It should be appreciated that the organization of the contentsof the medium 720 and/or memory 704 as shown in user device 700 ismerely exemplary, and as such the functionality of the modules and/ordata structures may be combined, separated, and/or be structured indifferent ways depending upon the implementation of the user device 700.

The medium 720 and/or memory 704 may include transportation requestmodule 722 that when implemented by the one or more processors 702configures the one or more processors 702 to transmit a transportationrequest message to a transportation entity, e.g., via transceiver 710 ortransceiver 740. The transportation request message may include one ormore message information elements including an identifier for the userdevice 700, a type of transport vehicle requested, a number of users,and a requested destination, which may be user selected. Thetransportation request message may further include one or more of avalidity time for the transportation request message, a maximum traveltime or required destination arrival time, a user type, a willingness toshare transport vehicle, a maximum fare, a requested departure time, abeacon proximity threshold, or a combination thereof.

The medium 720 and/or memory 704 may include a transportation responsemodule 724 that that when implemented by the one or more processors 702configures the one or more processors 702 to receive a transportationresponse message from the transportation entity, e.g., via transceiver710 or transceiver 740. The transportation response message may includeone or more message information elements including an acceptance orrejection of the transportation request message. The transportationresponse message may further include at least one of a transportationtype, a transportation identifier, a fare, an indication of whether thetransportation is shared or individual, an estimated time of arrival forpickup and an estimated time of arrival to destination, or a combinationthereof.

The medium 720 and/or memory 704 may include transportation confirmmodule 726 that when implemented by the one or more processors 702configures the one or more processors 702 to transmit a transportationconfirm message to the transportation entity in response to anacceptance in the transportation response message, e.g., via transceiver710 or transceiver 740. The transportation confirm message may includeone or more message information elements including the identifier forthe user device. The transportation confirm message may further includeat least one of the requested destination and estimated time of arrivalfor pickup, or a combination thereof.

The medium 720 and/or memory 704 may include a status request module 728that when implemented by the one or more processors 702 configures theone or more processors 702 to transmit a status request message to thetransportation entity, e.g., via transceiver 710 or transceiver 740,e.g., in response to a user input. The status request message mayinclude one or more message information elements including a query forinformation related to a current location or an identifier for the userdevice 700 and a query for information related to an estimate of arrivalto the requested destination.

The medium 720 and/or memory 704 may include a status module 730 thatwhen implemented by the one or more processors 702 configures the one ormore processors 702 to receive a status message from the transportationentity, e.g., via transceiver 710 or transceiver 740, e.g., in responseto a status request message. The transportation status message mayinclude one or more message information elements including informationrelated to the current location or an estimate of arrival todestination. The estimate of arrival to destination may be an estimatedtime of arrival to destination or an estimated number of stops todestination. The transportation status message may include a destinationof the transport vehicle nearest the requested destination.

The medium 720 and/or memory 704 may include an estimate of arrivalmodule 731 that when implemented by the one or more processors 702configures the one or more processors 702 to determine an estimate ofarrival to the requested destination using the information related tothe current location. For example, based on the current location, anestimated time of arrival to the destination or estimated number ofstops may be to the destination may be determined.

The medium 720 and/or memory 704 may include a complete request module732 that when implemented by the one or more processors 702 configuresthe one or more processors 702 to transmit a complete request message tothe transportation entity, e.g., via transceiver 710 or transceiver 740,e.g., in response to a user input. The complete request message mayinclude one or more message information elements including an identifierfor the user device 700 and a request to disembark.

The medium 720 and/or memory 704 may include a complete acknowledgementmodule 734 that when implemented by the one or more processors 702configures the one or more processors 702 to receive a completeacknowledgement message from the transportation entity, e.g., viatransceiver 710 or transceiver 740, e.g., in response to the completerequest message. The complete acknowledgement message may include one ormore message information elements including an estimate of arrival todestination and a confirmation of the request to disembark.

The medium 720 and/or memory 704 may include a complete response module736 that when implemented by the one or more processors 702 configuresthe one or more processors 702 to receive a complete response messagefrom the transportation entity, e.g., via transceiver 710 or transceiver740, e.g., in response to the complete request message. The completeresponse message may include one or more message information elementsincluding the identifier for the user device, an ingress location, anegress location, and a fare. The complete response message may furtherinclude a request to provide periodic signals to validate that the userdevice has exited the transport vehicle.

The methodologies described herein may be implemented by various meansdepending upon the application. For example, these methodologies may beimplemented in hardware, firmware, software, or any combination thereof.For a hardware implementation, the one or more processors 702 may beimplemented within one or more application specific integrated circuits(ASICs), digital signal processors (DSPs), digital signal processingdevices (DSPDs), programmable logic devices (PLDs), field programmablegate arrays (FPGAs), processors, controllers, micro-controllers,microprocessors, electronic devices, other electronic units designed toperform the functions described herein, or a combination thereof.

For a firmware and/or software implementation, the methodologies may beimplemented with modules (e.g., procedures, functions, and so on) thatperform the functions described herein. Any machine readable mediumtangibly embodying instructions may be used in implementing themethodologies described herein. For example, software codes may bestored in a non-transitory computer readable medium 720 or memory 704that is connected to and executed by the one or more processors 702.Memory may be implemented within the one or more processors or externalto the one or more processors. As used herein the term “memory” refersto any type of long term, short term, volatile, nonvolatile, or othermemory and is not to be limited to any particular type of memory ornumber of memories, or type of media upon which memory is stored.

If implemented in firmware and/or software, the functions may be storedas one or more instructions or program code 708 on a non-transitorycomputer readable medium, such as medium 720 and/or memory 704. Examplesinclude computer readable media encoded with a data structure andcomputer readable media encoded with a computer program 708. Forexample, the non-transitory computer readable medium including programcode 708 stored thereon may include program code 708 to support OTDOAmeasurements in a manner consistent with disclosed embodiments.Non-transitory computer readable medium 720 includes physical computerstorage media. A storage medium may be any available medium that can beaccessed by a computer. By way of example, and not limitation, suchnon-transitory computer readable media can comprise RAM, ROM, EEPROM,CD-ROM or other optical disk storage, magnetic disk storage or othermagnetic storage devices, or any other medium that can be used to storedesired program code 708 in the form of instructions or data structuresand that can be accessed by a computer; disk and disc, as used herein,includes compact disc (CD), laser disc, optical disc, digital versatiledisc (DVD), floppy disk and Blu-ray disc where disks usually reproducedata magnetically, while discs reproduce data optically with lasers.Combinations of the above should also be included within the scope ofcomputer readable media.

In addition to storage on computer readable medium 720, instructionsand/or data may be provided as signals on transmission media included ina communication apparatus. For example, a communication apparatus mayinclude a transceiver 710 having signals indicative of instructions anddata. The instructions and data are configured to cause one or moreprocessors to implement the functions outlined in the claims. That is,the communication apparatus includes transmission media with signalsindicative of information to perform disclosed functions.

Memory 704 may represent any data storage mechanism. Memory 704 mayinclude, for example, a primary memory and/or a secondary memory.Primary memory may include, for example, a random access memory, readonly memory, etc. While illustrated in this example as being separatefrom one or more processors 702, it should be understood that all orpart of a primary memory may be provided within or otherwiseco-located/coupled with the one or more processors 702. Secondary memorymay include, for example, the same or similar type of memory as primarymemory and/or one or more data storage devices or systems, such as, forexample, a disk drive, an optical disc drive, a tape drive, a solidstate memory drive, etc.

In certain implementations, secondary memory may be operativelyreceptive of, or otherwise configurable to couple to a non-transitorycomputer readable medium 720. As such, in certain exampleimplementations, the methods and/or apparatuses presented herein maytake the form in whole or part of a computer readable medium 720 thatmay include computer implementable code 708 stored thereon, which ifexecuted by one or more processors 702 may be operatively enabled toperform all or portions of the example operations as described herein.Computer readable medium 720 may be a part of memory 704.

Thus, a user device, such as user device 700, may include a means fortransmitting a transportation request message to a transportation entitywirelessly, the transportation request message comprises one or moremessage information elements including an identifier for the user deviceand a requested destination, which may be, e.g., the wirelesstransceiver 710 or wireless transceiver 740 and one or more processors702 with dedicated hardware or implementing executable code or softwareinstructions in medium 720 and/or memory 704 such as the transportationrequest module 722. A means for receiving a transportation responsemessage from the transportation entity wirelessly, the transportationresponse message comprises one or more message information elementsincluding acceptance or rejection of the transportation request messagemay be, e.g., the wireless transceiver 710 or wireless transceiver 740and one or more processors 702 with dedicated hardware or implementingexecutable code or software instructions in medium 720 and/or memory 704such as the transportation response module 724. A means for transmittinga transportation confirm message to the transportation entity wirelesslyin response to the acceptance in the transportation response message,the transportation confirm message comprises one or more messageinformation elements including the identifier for the user device maybe, e.g., the wireless transceiver 710 or wireless transceiver 740 andone or more processors 702 with dedicated hardware or implementingexecutable code or software instructions in medium 720 and/or memory 704such as the transportation confirm module 726.

In one implementation, the user device may further include a means fortransmitting a transportation status request message to thetransportation entity wirelessly, the transportation status requestmessage comprises one or more message information elements including aquery for information related to a current location, which may be, e.g.,the wireless transceiver 710 or wireless transceiver 740 and one or moreprocessors 702 with dedicated hardware or implementing executable codeor software instructions in medium 720 and/or memory 704 such as thestatus request module 728. A means for receiving a transportation statusmessage from the transportation entity wirelessly, the transportationstatus message comprises one or more message information elementsincluding information related to the current location may be, e.g., thewireless transceiver 710 or wireless transceiver 740 and one or moreprocessors 702 with dedicated hardware or implementing executable codeor software instructions in medium 720 and/or memory 704 such as thestatus module 730. The user device may further include a means fordetermining an estimate of arrival to the requested destination usingthe information related to the current location, which may be, e.g., theone or more processors 702 with dedicated hardware or implementingexecutable code or software instructions in medium 720 and/or memory 704such as the estimate of arrival module 731.

In one implementation, the user device may further include a means fortransmitting a transportation status request message to thetransportation entity wirelessly, the transportation status requestmessage comprises one or more message information elements including theidentifier for the user device and a query for information related to anestimate of arrival to the requested destination, which may be, e.g.,the wireless transceiver 710 or wireless transceiver 740 and one or moreprocessors 702 with dedicated hardware or implementing executable codeor software instructions in medium 720 and/or memory 704 such as thestatus request module 728. A means for receiving a transportation statusmessage from the transportation entity wirelessly, the transportationstatus message comprises one or more message information elementsincluding the estimate of arrival to destination may be, e.g., thewireless transceiver 710 or wireless transceiver 740 and one or moreprocessors 702 with dedicated hardware or implementing executable codeor software instructions in medium 720 and/or memory 704 such as thestatus module 730.

In one implementation, the user device may further include a means fortransmitting a transportation complete request message to thetransportation entity wirelessly, the transportation status requestmessage comprises one or more message information elements including theidentifier for the user device, and a request to disembark, which maybe, e.g., the wireless transceiver 710 or wireless transceiver 740 andone or more processors 702 with dedicated hardware or implementingexecutable code or software instructions in medium 720 and/or memory 704such as the complete request module 732. A means for receiving atransportation complete acknowledgement message from the transportationentity wirelessly, the transportation complete acknowledgement messagecomprises one or more message information elements including an estimateof arrival to destination and a confirmation of the request to disembarkmay be, e.g., the wireless transceiver 710 or wireless transceiver 740and one or more processors 702 with dedicated hardware or implementingexecutable code or software instructions in medium 720 and/or memory 704such as the complete acknowledgement module 734. A means for receiving atransportation complete response message from the transportation entitywirelessly, the transportation complete response message comprises oneor more message information elements includes the identifier for theuser device, an ingress location, and an egress location may be, e.g.,the wireless transceiver 710 or wireless transceiver 740 and one or moreprocessors 702 with dedicated hardware or implementing executable codeor software instructions in medium 720 and/or memory 704 such as thecomplete response module 736.

FIG. 8 shows a schematic block diagram illustrating certain exemplaryfeatures of a schematic block diagram illustrating certain exemplaryfeatures of a transportation entity 800, which may be, e.g., a transportvehicle 110 or transport server 220 shown in FIGS. 1-3 , which isconfigured to perform an information exchange for a transportationservice with a user device, such as user device 102. In someembodiments, transportation entity 800 may include, for example, one ormore processors 802, memory 804, a transceiver 810 (e.g., wirelessinterface), and (as applicable) communications interface 806 (e.g.,wireline or wireless interface to other transportation entities, e.g.,to a transport vehicle 110 or transport server 220), which may beoperatively coupled with one or more connections 806 (e.g., buses,lines, fibers, links, etc.) to non-transitory computer readable medium820 and memory 804. In certain example implementations, some portion oftransportation entity 800 may take the form of a chipset, and/or thelike.

Transceiver 810 may, for example, include a transmitter 812 enabled totransmit one or more signals over one or more types of wirelesscommunication links and a receiver 814 to receive one or more signalstransmitted over the one or more types of wireless communication links.The transceiver 810 enables the transportation entity 800 to communicatewith user devices using D2D communication links, such as DSRC, C-V2X, or5G NR. Transportation entity 800 may include antenna 811 to transmitand/or receive signals processed by transceiver 810. Communicationsinterface 840 may include a variety of wired and wireless connectionsthat support wired transmission and/or reception and, if desired, mayadditionally or alternatively support transmission and reception of oneor more signals over one or more types of wireless communicationsystems. Communications interface 806 may also include interfaces forcommunication with various other computers and peripherals. For example,in one embodiment, communications interface 806 may comprise networkinterface cards, input-output cards, chips and/or ASICs that implementone or more of the communication functions performed by transportationentity 800.

The one or more processors 802 may be implemented using a combination ofhardware, firmware, and software. For example, one or more processors802 may be configured to perform the functions discussed herein byimplementing one or more instructions or program code 808 on anon-transitory computer readable medium, such as medium 820 and/ormemory 804. In some embodiments, the one or more processors 802 mayrepresent one or more circuits configurable to perform at least aportion of a data signal computing procedure or process related to theoperation of transportation entity 800.

The medium 820 and/or memory 804 may store instructions or program code808 that contain executable code or software instructions that whenexecuted by the one or more processors 802 cause the one or moreprocessors 802 to operate as a special purpose computer programmed toperform the techniques disclosed herein. As illustrated intransportation entity 800, the medium 820 and/or memory 804 may includeone or more components or modules that may be implemented by the one ormore processors 802 to perform the methodologies described herein. Whilethe components or modules are illustrated as software in medium 820 thatis executable by the one or more processors 802, it should be understoodthat the components or modules may be stored in memory 804 or may bededicated hardware either in the one or more processors 802 or off theprocessors.

A number of software modules and data tables may reside in the medium820 and/or memory 804 and be utilized by the one or more processors 802in order to manage both communications and the functionality describedherein. It should be appreciated that the organization of the contentsof the medium 820 and/or memory 804 as shown in mobile device 82 ismerely exemplary, and as such the functionality of the modules and/ordata structures may be combined, separated, and/or be structured indifferent ways depending upon the implementation of the transportationentity 800.

The medium 820 and/or memory 804 may include transportation requestmodule 722 that when implemented by the one or more processors 702configures the one or more processors 702 to receive a transportationrequest message from a user device 102, e.g., via transceiver 710. Thetransportation request message may include one or more messageinformation elements including an identifier for the user device, a typeof transport vehicle requested, a number of users, and a requesteddestination. The transportation request message may further include oneor more of a validity time for the transportation request message, amaximum travel time or required destination arrival time, a user type, awillingness to share transport vehicle, a maximum fare, a requesteddeparture time, a beacon proximity threshold, or a combination thereof.

The medium 820 and/or memory 804 may include a transportation responsemodule 824 that that when implemented by the one or more processors 802configures the one or more processors 802 to transmit a transportationresponse message to the user device 102, e.g., via transceiver 810. Thetransportation response message may include one or more messageinformation elements including an acceptance or rejection of thetransportation request message. The transportation response message mayfurther include at least one of a transportation type, a transportationidentifier, a fare, an indication of whether the transportation isshared or individual, an estimated time of arrival for pickup and anestimated time of arrival to destination, or a combination thereof.

The medium 820 and/or memory 804 may include transportation confirmmodule 826 that when implemented by the one or more processors 802configures the one or more processors 802 to receive a transportationconfirm message from the user device 102 in response to an acceptance inthe transportation response message, e.g., via transceiver 810. Thetransportation confirm message may include one or more messageinformation elements including the identifier for the user device. Thetransportation confirm message may further include at least one of therequested destination and estimated time of arrival for pickup, or acombination thereof.

The medium 820 and/or memory 804 may include a status request module 828that when implemented by the one or more processors 802 configures theone or more processors 802 to receive a status request message from theuser device 102, e.g., via transceiver 810. The status request messagemay include one or more message information elements including a queryfor information related to a current location or an identifier for theuser device 800 and a query for information related to an estimate ofarrival to the requested destination.

The medium 820 and/or memory 804 may include a status module 830 thatwhen implemented by the one or more processors 802 configures the one ormore processors 802 to transmit a status message to the user device 102,e.g., via transceiver 810, e.g., in response to a status requestmessage. The transportation status message may include one or moremessage information elements including information related to thecurrent location or an estimate of arrival to destination. The estimateof arrival to destination may be an estimated time of arrival todestination or an estimated number of stops to destination. Thetransportation status message may include a destination of the transportvehicle nearest the requested destination

The medium 820 and/or memory 804 may include a complete request module832 that when implemented by the one or more processors 802 configuresthe one or more processors 802 to receive a complete request messagefrom the user device 102, e.g., via transceiver 810. The completerequest message may include one or more message information elementsincluding an identifier for the user device 800 and a request todisembark.

The medium 820 and/or memory 804 may include a complete acknowledgementmodule 834 that when implemented by the one or more processors 802configures the one or more processors 802 to transmit a completeacknowledgement message to the user device 102, e.g., via transceiver810, e.g., in response to the complete request message. The completeacknowledgement message may include one or more message informationelements including an estimate of arrival to destination and aconfirmation of the request to disembark.

The medium 820 and/or memory 804 may include a complete response module836 that when implemented by the one or more processors 802 configuresthe one or more processors 802 to transmit a complete response messageto the user device 102, e.g., via transceiver 810, e.g., in response tothe complete request message. The complete response message may includeone or more message information elements including the identifier forthe user device, an ingress location, an egress location, and a fare.The complete response message may further include a request to provideperiodic signals to validate that the user device has exited thetransport vehicle.

The methodologies described herein may be implemented by various meansdepending upon the application. For example, these methodologies may beimplemented in hardware, firmware, software, or any combination thereof.For a hardware implementation, the one or more processors 802 may beimplemented within one or more application specific integrated circuits(ASICs), digital signal processors (DSPs), digital signal processingdevices (DSPDs), programmable logic devices (PLDs), field programmablegate arrays (FPGAs), processors, controllers, micro-controllers,microprocessors, electronic devices, other electronic units designed toperform the functions described herein, or a combination thereof.

For a firmware and/or software implementation, the methodologies may beimplemented with modules (e.g., procedures, functions, and so on) thatperform the functions described herein. Any machine readable mediumtangibly embodying instructions may be used in implementing themethodologies described herein. For example, software codes may bestored in a non-transitory computer readable medium 820 or memory 804that is connected to and executed by the one or more processors 802.Memory may be implemented within the one or more processors or externalto the one or more processors. As used herein the term “memory” refersto any type of long term, short term, volatile, nonvolatile, or othermemory and is not to be limited to any particular type of memory ornumber of memories, or type of media upon which memory is stored.

If implemented in firmware and/or software, the functions may be storedas one or more instructions or program code 808 on a non-transitorycomputer readable medium, such as medium 820 and/or memory 804. Examplesinclude computer readable media encoded with a data structure andcomputer readable media encoded with a computer program 808. Forexample, the non-transitory computer readable medium including programcode 808 stored thereon may include program code 808 to support OTDOAmeasurements in a manner consistent with disclosed embodiments.Non-transitory computer readable medium 820 includes physical computerstorage media. A storage medium may be any available medium that can beaccessed by a computer. By way of example, and not limitation, suchnon-transitory computer readable media can comprise RAM, ROM, EEPROM,CD-ROM or other optical disk storage, magnetic disk storage or othermagnetic storage devices, or any other medium that can be used to storedesired program code 808 in the form of instructions or data structuresand that can be accessed by a computer; disk and disc, as used herein,includes compact disc (CD), laser disc, optical disc, digital versatiledisc (DVD), floppy disk and Blu-ray disc where disks usually reproducedata magnetically, while discs reproduce data optically with lasers.Combinations of the above should also be included within the scope ofcomputer readable media.

In addition to storage on computer readable medium 820, instructionsand/or data may be provided as signals on transmission media included ina communication apparatus. For example, a communication apparatus mayinclude a transceiver 810 having signals indicative of instructions anddata. The instructions and data are configured to cause one or moreprocessors to implement the functions outlined in the claims. That is,the communication apparatus includes transmission media with signalsindicative of information to perform disclosed functions.

Memory 804 may represent any data storage mechanism. Memory 804 mayinclude, for example, a primary memory and/or a secondary memory.Primary memory may include, for example, a random access memory, readonly memory, etc. While illustrated in this example as being separatefrom one or more processors 802, it should be understood that all orpart of a primary memory may be provided within or otherwiseco-located/coupled with the one or more processors 802. Secondary memorymay include, for example, the same or similar type of memory as primarymemory and/or one or more data storage devices or systems, such as, forexample, a disk drive, an optical disc drive, a tape drive, a solidstate memory drive, etc.

In certain implementations, secondary memory may be operativelyreceptive of, or otherwise configurable to couple to a non-transitorycomputer readable medium 820. As such, in certain exampleimplementations, the methods and/or apparatuses presented herein maytake the form in whole or part of a computer readable medium 820 thatmay include computer implementable code 808 stored thereon, which ifexecuted by one or more processors 802 may be operatively enabled toperform all or portions of the example operations as described herein.Computer readable medium 820 may be a part of memory 804.

Thus, a transportation entity, e.g., transportation entity 800, mayinclude a means for receiving a transportation request message from auser device wirelessly, the transportation request message comprises oneor more message information elements including an identifier for theuser device and a requested destination, which may be, e.g., thetransceiver 810 and one or more processors 802 with dedicated hardwareor implementing executable code or software instructions in medium 820and/or memory 804 such as the transportation request module 822. A meansfor transmitting a transportation response message to the user devicewirelessly, the transportation response message comprises one or moremessage information elements including acceptance or rejection of thetransportation request message may be, e.g., the transceiver 810 and oneor more processors 802 with dedicated hardware or implementingexecutable code or software instructions in medium 820 and/or memory 804such as the transportation response module 824. A means for receiving atransportation confirm message from the user device wirelessly inresponse to the acceptance in the transportation response message, thetransportation confirm message comprises one or more message informationelements including the identifier for the user device may be, e.g., thetransceiver 810 and one or more processors 802 with dedicated hardwareor implementing executable code or software instructions in medium 820and/or memory 804 such as the transportation confirm module 826.

In one implementation, the transportation entity may include a means forreceiving a transportation status request message from the user devicewirelessly, the transportation status request message comprises one ormore message information elements including a query for informationrelated to a current location, which may be, e.g., the transceiver 810and one or more processors 802 with dedicated hardware or implementingexecutable code or software instructions in medium 820 and/or memory 804such as the status request module 828. A means for transmitting atransportation status message to the user device wirelessly, thetransportation status message comprises one or more message informationelements including information related to the current location may be,e.g., the transceiver 810 and one or more processors 802 with dedicatedhardware or implementing executable code or software instructions inmedium 820 and/or memory 804 such as the status module 830.

In one implementation, the transportation entity may include a means forreceiving a transportation status request message from the user devicewirelessly, the transportation status request message comprises one ormore message information elements including the identifier for the userdevice and a query for information related to an estimate of arrival tothe requested destination, which may be, e.g., the transceiver 810 andone or more processors 802 with dedicated hardware or implementingexecutable code or software instructions in medium 820 and/or memory 804such as the status request module 828. A means for transmitting atransportation status message to the user device wirelessly, thetransportation status message comprises one or more message informationelements including the estimate of arrival to destination may be, e.g.,the transceiver 810 and one or more processors 802 with dedicatedhardware or implementing executable code or software instructions inmedium 820 and/or memory 804 such as the status module 830.

In one implementation, the transportation entity may include a means forreceiving a transportation complete request message from the user devicewirelessly, the transportation status request message comprises one ormore message information elements including the identifier for the userdevice, and a request to disembark, which may be, e.g., the transceiver810 and one or more processors 802 with dedicated hardware orimplementing executable code or software instructions in medium 820and/or memory 804 such as the complete request module 832. A means fortransmitting a transportation complete acknowledgement message to theuser device wirelessly, the transportation complete acknowledgementmessage comprises one or more message information elements including anestimate of arrival to destination and a confirmation of the request todisembark may be, e.g., the transceiver 810 and one or more processors802 with dedicated hardware or implementing executable code or softwareinstructions in medium 820 and/or memory 804 such as the completeacknowledgement module 834. A means for transmitting a transportationcomplete response message to the user device wirelessly, thetransportation complete response message comprises one or more messageinformation elements including the identifier for the user device, aningress location, and an egress location may be, e.g., the transceiver810 and one or more processors 802 with dedicated hardware orimplementing executable code or software instructions in medium 820and/or memory 804 such as the complete response module 836.

Reference throughout this specification to “one example”, “an example”,“certain examples”, or “exemplary implementation” means that aparticular feature, structure, or characteristic described in connectionwith the feature and/or example may be included in at least one featureand/or example of claimed subject matter. Thus, the appearances of thephrase “in one example”, “an example”, “in certain examples” or “incertain implementations” or other like phrases in various placesthroughout this specification are not necessarily all referring to thesame feature, example, and/or limitation. Furthermore, the particularfeatures, structures, or characteristics may be combined in one or moreexamples and/or features.

Some portions of the detailed description included herein are presentedin terms of algorithms or symbolic representations of operations onbinary digital signals stored within a memory of a specific apparatus orspecial purpose computing device or platform. In the context of thisparticular specification, the term specific apparatus or the likeincludes a general purpose computer once it is programmed to performparticular operations pursuant to instructions from program software.Algorithmic descriptions or symbolic representations are examples oftechniques used by those of ordinary skill in the signal processing orrelated arts to convey the substance of their work to others skilled inthe art. An algorithm is here, and generally, is considered to be aself-consistent sequence of operations or similar signal processingleading to a desired result. In this context, operations or processinginvolve physical manipulation of physical quantities. Typically,although not necessarily, such quantities may take the form ofelectrical or magnetic signals capable of being stored, transferred,combined, compared or otherwise manipulated. It has proven convenient attimes, principally for reasons of common usage, to refer to such signalsas bits, data, values, elements, symbols, characters, terms, numbers,numerals, or the like. It should be understood, however, that all ofthese or similar terms are to be associated with appropriate physicalquantities and are merely convenient labels. Unless specifically statedotherwise, as apparent from the discussion herein, it is appreciatedthat throughout this specification discussions utilizing terms such as“processing,” “computing,” “calculating,” “determining” or the likerefer to actions or processes of a specific apparatus, such as a specialpurpose computer, special purpose computing apparatus or a similarspecial purpose electronic computing device. In the context of thisspecification, therefore, a special purpose computer or a similarspecial purpose electronic computing device is capable of manipulatingor transforming signals, typically represented as physical electronic ormagnetic quantities within memories, registers, or other informationstorage devices, transmission devices, or display devices of the specialpurpose computer or similar special purpose electronic computing device.

In the preceding detailed description, numerous specific details havebeen set forth to provide a thorough understanding of claimed subjectmatter. However, it will be understood by those skilled in the art thatclaimed subject matter may be practiced without these specific details.In other instances, methods and apparatuses that would be known by oneof ordinary skill have not been described in detail so as not to obscureclaimed subject matter.

The terms, “and”, “or”, and “and/or” as used herein may include avariety of meanings that also are expected to depend at least in partupon the context in which such terms are used. Typically, “or” if usedto associate a list, such as A, B or C, is intended to mean A, B, and C,here used in the inclusive sense, as well as A, B or C, here used in theexclusive sense. In addition, the term “one or more” as used herein maybe used to describe any feature, structure, or characteristic in thesingular or may be used to describe a plurality or some othercombination of features, structures or characteristics. Though, itshould be noted that this is merely an illustrative example and claimedsubject matter is not limited to this example.

While there has been illustrated and described what are presentlyconsidered to be example features, it will be understood by thoseskilled in the art that various other modifications may be made, andequivalents may be substituted, without departing from claimed subjectmatter. Additionally, many modifications may be made to adapt aparticular situation to the teachings of claimed subject matter withoutdeparting from the central concept described herein.

Implementation examples are described in the following numbered clauses:

1. A method of performing information exchange for a transportationservice by a user device, the method comprising:

transmitting a transportation request message to a transportation entitywirelessly, the transportation request message comprises one or moremessage information elements including an identifier for the user deviceand a requested destination;

receiving a transportation response message from the transportationentity wirelessly, the transportation response message comprises one ormore message information elements including acceptance or rejection ofthe transportation request message; and

transmitting a transportation confirm message to the transportationentity wirelessly in response to the acceptance in the transportationresponse message, the transportation confirm message comprises one ormore message information elements including the identifier for the userdevice.

2. The method of clause 1, wherein the transportation request message,the transportation response message, and the transportation confirmmessage are dedicated messages in a Device-to-Device (D2D) communicationlink, comprising one or more of a dedicated short-range communication(DSRC), a cellular Vehicle-to-Everything (C-V2X) communication, or a 5GNew Radio (NR) communication.

3. The method of clause 1, wherein the transportation request message,the transportation response message, and the transportation confirmmessage are encapsulated in data payloads in a Device-to-Device (D2D)communication link, comprising one or more of a dedicated short-rangecommunication (DSRC), a cellular Vehicle-to-Everything (C-V2X)communication, or a 5G New Radio (NR) communication.

4. The method of any of clauses 1-3, wherein the one or more messageinformation elements in the transportation request message furthercomprise at least one of a type of transport device requested, a numberof users, a validity time for the transportation request message, amaximum travel time or required destination arrival time, or acombination thereof.

5. The method of any of clauses 1-4, wherein the one or more messageinformation elements in the transportation request message furthercomprise at least one of a user type, a willingness to share transportvehicle, a maximum fare, a requested departure time, a beacon proximitythreshold, or a combination thereof.

6. The method of any of clauses 1-5, wherein the one or more messageinformation elements in the transportation response message furthercomprise at least one of a transportation type, a transportationidentifier, a fare, an indication of whether the transportation isshared or individual, an estimated time of arrival for pickup and anestimated time of arrival to destination, or a combination thereof.

7. The method of any of clauses 1-6, wherein the one or more messageinformation elements in the transportation confirm message furthercomprise at least one of the requested destination and estimated time ofarrival for pickup, or a combination thereof.

8. The method of any of clauses 1-7, further comprising:

transmitting a transportation status request message to thetransportation entity wirelessly, the transportation status requestmessage comprises one or more message information elements including aquery for information related to a current location; and

receiving a transportation status message from the transportation entitywirelessly, the transportation status message comprises one or moremessage information elements including information related to thecurrent location.

9. The method of clause 8, further comprising determining an estimate ofarrival to the requested destination using the information related tothe current location.

10. The method of any of clauses 1-9, further comprising:

transmitting a transportation status request message to thetransportation entity wirelessly, the transportation status requestmessage comprises one or more message information elements including theidentifier for the user device, a query for information related to anestimate of arrival to the requested destination; and

receiving a transportation status message from the transportation entitywirelessly, the transportation status message comprises one or moremessage information elements including the estimate of arrival todestination.

11. The method of clause 10, wherein the estimate of arrival todestination comprises one or more of estimated time of arrival todestination and estimated number of stops to destination.

12. The method of clause 10, wherein the one or more message informationelements in the transportation status message further includes adestination of the transport vehicle nearest the requested destination.

13. The method of any of clauses 1-12, further comprising:

transmitting a transportation complete request message to thetransportation entity wirelessly, the transportation complete requestmessage comprises one or more message information elements including theidentifier for the user device, and a request to disembark;

receiving a transportation complete acknowledgement message from thetransportation entity wirelessly, the transportation completeacknowledgement message comprises one or more message informationelements including an estimate of arrival to destination and aconfirmation of the request to disembark.

14. The method of clause 13, further comprising:

receiving a transportation complete response message from thetransportation entity wirelessly, the transportation complete responsemessage comprises one or more message information elements includes theidentifier for the user device, an ingress location, and an egresslocation.

15. The method of clause 14, wherein the transportation completeresponse message further comprises one or more message informationelements including at least one of a fare and a request to provideperiodic signals to validate that the user device has exited thetransport vehicle.

16. The method of any of clauses 1-15, wherein the transportation entitycomprises a transport vehicle, a transport server, or both.

17. A user device configured to perform information exchange for atransportation service, the user device comprising:

a wireless transceiver configured to communicate with a transportationentity wirelessly;

at least one memory; and

at least one processor coupled to the wireless transceiver and the atleast one memory, the at least one processor configured to:

transmit a transportation request message to the transportation entity,via the wireless transceiver, the transportation request messagecomprises one or more message information elements including anidentifier for the user device, and a requested destination;

receive a transportation response message from the transportationentity, via the wireless transceiver, the transportation responsemessage comprises one or more message information elements includingacceptance or rejection of the transportation request message; and

transmit a transportation confirm message to the transportation entity,via the wireless transceiver, in response to the acceptance in thetransportation response message, the transportation confirm messagecomprises one or more message information elements including theidentifier for the user device.

18. The user device of clause 17, wherein the transportation requestmessage, the transportation response message, and the transportationconfirm message are dedicated messages in a Device-to-Device (D2D)communication link, comprising one or more of a dedicated short-rangecommunication (DSRC), a cellular Vehicle-to-Everything (C-V2X)communication, or a 5G New Radio (NR) communication.

19. The user device of clause 17, wherein the transportation requestmessage, the transportation response message, and the transportationconfirm message are encapsulated in data payloads in a Device-to-Device(D2D) communication link, comprising one or more of a dedicatedshort-range communication (DSRC), a cellular Vehicle-to-Everything(C-V2X) communication, or a 5G New Radio (NR) communication.

20. The user device of any of clauses 17-19, wherein the one or moremessage information elements in the transportation request messagefurther comprise at least one of a type of transport device requested, anumber of users, a validity time for the transportation request message,a maximum travel time or required destination arrival time, or acombination thereof.

21. The user device of any of clauses 17-20, wherein the one or moremessage information elements in the transportation request messagefurther comprise at least one of a user type, a willingness to sharetransport vehicle, a maximum fare, a requested departure time, a beaconproximity threshold, or a combination thereof.

22. The user device of any of clauses 17-21, wherein the one or moremessage information elements in the transportation response messagefurther comprise at least one of a transportation type, a transportationidentifier, a fare, an indication of whether the transportation isshared or individual, an estimated time of arrival for pickup and anestimated time of arrival to destination, or a combination thereof.

23. The user device of any of clauses 17-22, wherein the one or moremessage information elements in the transportation confirm messagefurther comprise at least one of the requested destination and estimatedtime of arrival for pickup, or a combination thereof.

24. The user device of any of clauses 17-23, wherein the at least oneprocessor is further configured to:

transmit, via the wireless transceiver, a transportation status requestmessage to the transportation entity, the transportation status requestmessage comprises one or more message information elements including aquery for information related to a current location; and

receive, via the wireless transceiver, a transportation status messagefrom the transportation entity, the transportation status messagecomprises one or more message information elements including informationrelated to the current location.

25. The user device of clause 24, wherein the at least one processor isfurther configured to determine an estimate of arrival to the requesteddestination using the information related to the current location.

26. The user device of any of clauses 17-25, wherein the at least oneprocessor is further configured to:

transmit a transportation status request message to the transportationentity, via the wireless transceiver, the transportation status requestmessage comprises one or more message information elements including theidentifier for the user device, a query for information related to anestimate of arrival to the requested destination; and

receive a transportation status message from the transportation entity,via the wireless transceiver, the transportation status messagecomprises one or more message information elements including theestimate of arrival to destination.

27. The user device of clause 26, wherein the estimate of arrival todestination comprises one or more of estimated time of arrival todestination and estimated number of stops to destination.

28. The user device of clause 26, wherein the one or more messageinformation elements in the transportation status message furtherincludes a destination of the transport vehicle nearest the requesteddestination.

29. The user device of any of clauses 17-28, wherein the at least oneprocessor is further configured to:

transmit a transportation complete request message to the transportationentity, via the wireless transceiver, the transportation completerequest message comprises one or more message information elementsincluding the identifier for the user device, and a request todisembark;

receive a transportation complete acknowledgement message from thetransportation entity, via the wireless transceiver, the transportationcomplete acknowledgement message comprises one or more messageinformation elements including an estimate of arrival to destination anda confirmation of the request to disembark.

30. The user device of clause 29, wherein the at least one processor isfurther configured to:

receive a transportation complete response message from thetransportation entity, via the wireless transceiver, the transportationcomplete response message comprises one or more message informationelements includes the identifier for the user device, an ingresslocation, and an egress location.

31. The user device of clause 30, wherein the transportation completeresponse message further comprises one or more message informationelements including at least one of a fare and a request to provideperiodic signals to validate that the user device has exited thetransport vehicle.

32. The user device of any of clauses 17-31, wherein the transportationentity comprises a transport vehicle, a transport server, or both.

33. A user device configured to perform information exchange for atransportation service, comprising:

means for transmitting a transportation request message to atransportation entity wirelessly, the transportation entity comprisingone or both of a transport vehicle and a transport server, thetransportation request message comprises one or more message informationelements including an identifier for the user device, and a requesteddestination;

means for receiving a transportation response message from thetransportation entity wirelessly, the transportation response messagecomprises one or more message information elements including acceptanceor rejection of the transportation request message; and

means for transmitting a transportation confirm message to thetransportation entity wirelessly in response to the acceptance in thetransportation response message, the transportation confirm messagecomprises one or more message information elements including theidentifier for the user device.

34. A non-transitory storage medium including program code storedthereon, the program code is operable to configure at least oneprocessor in a user device to perform information exchange for atransportation service, comprising:

program code to transmit a transportation request message to atransportation entity wirelessly, the transportation entity comprisingone or both of a transport vehicle and a transport server, thetransportation request message comprises one or more message informationelements including an identifier for the user device, and a requesteddestination;

program code to receive a transportation response message from thetransportation entity wirelessly, the transportation response messagecomprises one or more message information elements including acceptanceor rejection of the transportation request message; and

program code to transmit a transportation confirm message to thetransportation entity wirelessly in response to the acceptance in thetransportation response message, the transportation confirm messagecomprises one or more message information elements including theidentifier for the user device.

35. A method of performing information exchange for a transportationservice by a transportation entity, the method comprising:

receiving a transportation request message from a user devicewirelessly, the transportation request message comprises one or moremessage information elements including an identifier for the userdevice, and a requested destination;

transmitting a transportation response message to the user devicewirelessly, the transportation response message comprises one or moremessage information elements including acceptance or rejection of thetransportation request message; and

receiving a transportation confirm message from the user devicewirelessly in response to the acceptance in the transportation responsemessage, the transportation confirm message comprises one or moremessage information elements including the identifier for the userdevice.

36. The method of clause 35, wherein the transportation request message,the transportation response message, and the transportation confirmmessage are dedicated messages in a Device-to-Device (D2D) communicationlink, comprising one or more of a dedicated short-range communication(DSRC), a cellular Vehicle-to-Everything (C-V2X) communication, or a 5GNew Radio (NR) communication.

37. The method of clause 35, wherein the transportation request message,the transportation response message, and the transportation confirmmessage are encapsulated in data payloads in a Device-to-Device (D2D)communication link, comprising one or more of a dedicated short-rangecommunication (DSRC), a cellular Vehicle-to-Everything (C-V2X)communication, or a 5G New Radio (NR) communication.

38. The method of any of clauses 35-37, wherein the one or more messageinformation elements in the transportation request message furthercomprise at least one of a type of transport device requested, a numberof users, a validity time for the transportation request message, amaximum travel time or required destination arrival time, or acombination thereof.

39. The method of any of clauses 35-38, wherein the one or more messageinformation elements in the transportation request message furthercomprise at least one of a user type, a willingness to share transportvehicle, a maximum fare, a requested departure time, a beacon proximitythreshold, or a combination thereof.

40. The method of any of clauses 35-39, wherein the one or more messageinformation elements in the transportation response message furthercomprise at least one of a transportation type, a transportationidentifier, a fare, an indication of whether the transportation isshared or individual, an estimated time of arrival for pickup and anestimated time of arrival to destination, or a combination thereof.

41. The method of any of clauses 35-40, wherein the one or more messageinformation elements in the transportation confirm message furthercomprise at least one of the requested destination and estimated time ofarrival for pickup, or a combination thereof.

42. The method of any of clauses 35-41, further comprising:

receiving a transportation status request message from the user devicewirelessly, the transportation status request message comprises one ormore message information elements including a query for informationrelated to a current location; and

transmitting a transportation status message to the user devicewirelessly, the transportation status message comprises one or moremessage information elements including information related to thecurrent location.

43. The method of any of clauses 35-42, further comprising:

receiving a transportation status request message from the user devicewirelessly, the transportation status request message comprises one ormore message information elements including the identifier for the userdevice, a query for information related to an estimate of arrival to therequested destination; and

transmitting a transportation status message to the user devicewirelessly, the transportation status message comprises one or moremessage information elements including the estimate of arrival todestination.

44. The method of clause 43, wherein the estimate of arrival todestination comprises one or more of estimated time of arrival todestination and estimated number of stops to destination.

45. The method of clause 43, wherein the one or more message informationelements in the transportation status message further includes adestination of the transport vehicle nearest the requested destination.

46. The method of any of clauses 35-45, further comprising:

receiving a transportation complete request message from the user devicewirelessly, the transportation complete request message comprises one ormore message information elements including the identifier for the userdevice, and a request to disembark;

transmitting a transportation complete acknowledgement message to theuser device wirelessly, the transportation complete acknowledgementmessage comprises one or more message information elements including anestimate of arrival to destination and a confirmation of the request todisembark.

47. The method of clause 46, further comprising:

transmitting a transportation complete response message to the userdevice wirelessly, the transportation complete response messagecomprises one or more message information elements including theidentifier for the user device, an ingress location, and an egresslocation.

48. The method of clause 47, wherein the transportation completeresponse message further comprises one or more message informationelements including at least one of a fare and a request to provideperiodic signals to validate that the user device has exited thetransport vehicle.

49. The method of any of clauses 35-48, wherein the transportationentity comprises a transport vehicle, a transport server, or both.

50. A transportation entity configured to perform information exchangefor a transportation service, the transportation entity comprising one atransport vehicle and a transport server, the transportation entitycomprising:

a wireless transceiver configured to communicate with a user devicewirelessly;

at least one memory; and

at least one processor coupled to the wireless transceiver and the atleast one memory, the at least one processor configured to:

receive a transportation request message from the user device, via thewireless transceiver, the transportation request message comprises oneor more message information elements including an identifier for theuser device, and a requested destination;

transmit a transportation response message to the user device, via thewireless transceiver, the transportation response message comprises oneor more message information elements including acceptance or rejectionof the transportation request message; and

receive a transportation confirm message from the user device, via thewireless transceiver, in response to the acceptance in thetransportation response message, the transportation confirm messagecomprises one or more message information elements including theidentifier for the user device.

51. The transportation entity of clause 50, wherein the transportationrequest message, the transportation response message, and thetransportation confirm message are dedicated messages in aDevice-to-Device (D2D) communication link, comprising one or more of adedicated short-range communication (DSRC), a cellularVehicle-to-Everything (C-V2X) communication, or a 5G New Radio (NR)communication.

52. The transportation entity of clause 50, wherein the transportationrequest message, the transportation response message, and thetransportation confirm message are encapsulated in data payloads in aDevice-to-Device (D2D) communication link, comprising one or more of adedicated short-range communication (DSRC), a cellularVehicle-to-Everything (C-V2X) communication, or a 5G New Radio (NR)communication.

53. The transportation entity of any of clauses 50-52, wherein the oneor more message information elements in the transportation requestmessage further comprise at least one of a type of transport devicerequested, a number of users, a validity time for the transportationrequest message, a maximum travel time or required destination arrivaltime, or a combination thereof.

54. The transportation entity of any of clauses 50-53, wherein the oneor more message information elements in the transportation requestmessage further comprise at least one of a user type, a willingness toshare transport vehicle, a maximum fare, a requested departure time, abeacon proximity threshold, or a combination thereof.

55. The transportation entity of any of clauses 50-54, wherein the oneor more message information elements in the transportation responsemessage further comprise at least one of a transportation type, atransportation identifier, a fare, an indication of whether thetransportation is shared or individual, an estimated time of arrival forpickup and an estimated time of arrival to destination, or a combinationthereof.

56. The transportation entity of any of clauses 50-55, wherein the oneor more message information elements in the transportation confirmmessage further comprise at least one of the requested destination andestimated time of arrival for pickup, or a combination thereof.

57. The transportation entity of any of clauses 50-56, wherein the atleast one processor is further configured to:

receive, via the wireless transceiver, a transportation status requestmessage from the user device, the transportation status request messagecomprises one or more message information elements including a query forinformation related to a current location; and

transmit, via the wireless transceiver, a transportation status messageto the user device, the transportation status message comprises one ormore message information elements including information related to thecurrent location.

58. The transportation entity of any of clauses 50-57, wherein the atleast one processor is further configured to:

receive a transportation status request message from the user device,via the wireless transceiver, the transportation status request messagecomprises one or more message information elements including theidentifier for the user device, a query for information related to anestimate of arrival to the requested destination; and

transmit a transportation status message to the user device, via thewireless transceiver, the transportation status message comprises one ormore message information elements including the estimate of arrival todestination.

59. The transportation entity of clause 58, wherein the estimate ofarrival to destination comprises one or more of estimated time ofarrival to destination and estimated number of stops to destination.

60. The transportation entity of clause 58, wherein the one or moremessage information elements in the transportation status messagefurther includes a destination of the transport vehicle nearest therequested destination.

61. The transportation entity of any of clauses 50-60, wherein the atleast one processor is further configured to:

receive a transportation complete request message from the user device,via the wireless transceiver, the transportation complete requestmessage comprises one or more message information elements including theidentifier for the user device, and a request to disembark;

transmit a transportation complete acknowledgement message to the userdevice, via the wireless transceiver, the transportation completeacknowledgement message comprises one or more message informationelements including an estimate of arrival to destination and aconfirmation of the request to disembark.

62. The transportation entity of clause 61, wherein the at least oneprocessor is further configured to:

transmit a transportation complete response message to the user device,via the wireless transceiver, the transportation complete responsemessage comprises one or more message information elements including theidentifier for the user device, an ingress location, and an egresslocation.

63. The transportation entity of clause 62, wherein the transportationcomplete response message further comprises one or more messageinformation elements including at least one of a fare and a request toprovide periodic signals to validate that the user device has exited thetransport vehicle.

64. The transportation entity of any of clauses 50-63, wherein thetransportation entity comprises a transport vehicle, a transport server,or both.

65. A transportation entity configured to perform information exchangefor a transportation service, the transportation entity comprising:

means for receiving a transportation request message from a user devicewirelessly, the transportation request message comprises one or moremessage information elements including an identifier for the userdevice, and a requested destination;

means for transmitting a transportation response message to the userdevice wirelessly, the transportation response message comprises one ormore message information elements including an acceptance or rejectionof the transportation request message; and

means for receiving a transportation confirm message from the userdevice wirelessly in response to an acceptance in the transportationresponse message, the transportation confirm message comprises one ormore message information elements including the identifier for the userdevice.

66. A non-transitory storage medium including program code storedthereon, the program code is operable to configure at least oneprocessor in a transportation entity to perform information exchange fora transportation service, the non-transitory storage medium comprising:

program code to receive a transportation request message from a userdevice wirelessly, the transportation request message comprises one ormore message information elements including an identifier for the userdevice, and a requested destination;

program code to transmit a transportation response message to the userdevice wirelessly, the transportation response message comprises one ormore message information elements including an acceptance or rejectionof the transportation request message; and

program code to receive a transportation confirm message from the userdevice wirelessly in response to an acceptance in the transportationresponse message, the transportation confirm message comprises one ormore message information elements including the identifier for the userdevice.

Therefore, it is intended that claimed subject matter not be limited tothe particular examples disclosed, but that such claimed subject mattermay also include all aspects falling within the scope of appendedclaims, and equivalents thereof.

What is claimed is:
 1. A method of wireless communication at a userdevice, comprising: broadcasting a transportation request message to atransportation entity wirelessly, wherein the transportation requestmessage comprises a first set of message information elements includingan identifier for the user device and a requested destination; receivinga transportation response message broadcasted by the transportationentity wirelessly, wherein the transportation response message comprisesa second set of message information elements including acceptance orrejection of the transportation request message; transmitting atransportation confirm message to the transportation entity wirelesslyin response to the acceptance in the transportation response message,wherein the transportation confirm message comprises a third set ofmessage information elements including the identifier for the userdevice; broadcasting a transportation status request message to thetransportation entity wirelessly, wherein the transportation statusrequest message comprises a fourth set of message information elementsincluding a query for information related to a current location; andreceiving a transportation status message broadcasted by thetransportation entity wirelessly, wherein the transportation statusmessage comprises a fifth set of message information elements includinginformation related to the current location.
 2. The method of claim 1,wherein the first set of message information elements in thetransportation request message further comprises at least one of a typeof transport device requested, a number of users, a validity time forthe transportation request message, a maximum travel time or requireddestination arrival time, or a combination thereof.
 3. The method ofclaim 1, further comprising determining an estimate of arrival to therequested destination using the information related to the currentlocation.
 4. The method of claim 1, wherein the fourth set of messageinformation elements in the transportation status request messagefurther includes the identifier for the user device, a query forinformation related to an estimate of arrival to the requesteddestination, and wherein the fifth set of message information elementsin the transportation status message further includes the estimate ofarrival to destination.
 5. The method of claim 4, wherein the estimateof arrival to destination comprises one or more of estimated time ofarrival to destination and estimated number of stops to destination, andwherein the fifth set of message information elements in thetransportation status message further includes a destination of atransport vehicle nearest the requested destination.
 6. The method ofclaim 1, further comprising: broadcasting a transportation completerequest message to the transportation entity wirelessly, wherein thetransportation complete request message comprises a sixth set of messageinformation elements including the identifier for the user device, and arequest to disembark; receiving a transportation completeacknowledgement message broadcasted by the transportation entitywirelessly, wherein the transportation complete acknowledgement messagecomprises a seventh set of message information elements including anestimate of arrival to destination and a confirmation of the request todisembark; and receiving a transportation complete response messagebroadcasted by the transportation entity wirelessly, wherein thetransportation complete response message comprises an eighth set ofmessage information elements including the identifier for the userdevice, and including at least one of an ingress location, an egresslocation, a fare and a request to provide periodic signals to validatethat the user device has exited a transport vehicle.
 7. The method ofclaim 1, further comprising: transmitting a transport registrationmessage to the transportation entity, wherein the transport registrationmessage includes a payment method to be charged for transport; andreceiving a first acknowledgement message for the transportationregistration message from the transportation entity based on thetransport registration message, wherein the transportation requestmessage is broadcasted to the transportation entity based on the firstacknowledgement message.
 8. The method of claim 7, further comprising:transmitting a deregistration message to the transportation entity,wherein the deregistration message completes a purchase based on thepayment method.
 9. An apparatus for wireless communication at a userdevice, comprising: a memory; and at least one processor coupled to thememory and configured to: broadcast a transportation request message toa transportation entity wirelessly, wherein the transportation requestmessage comprises a first set of message information elements includingan identifier for the user device and a requested destination; receive atransportation response message broadcasted by the transportation entitywirelessly, wherein the transportation response message comprises asecond set of message information elements including acceptance orrejection of the transportation request message; transmit atransportation confirm message to the transportation entity wirelesslyin response to the acceptance in the transportation response message,wherein the transportation confirm message comprises a third set ofmessage information elements including the identifier for the userdevice; broadcast a transportation status request message to thetransportation entity wirelessly, wherein the transportation statusrequest message comprises a fourth set of message information elementsincluding a query for information related to a current location; andreceive a transportation status message broadcasted by thetransportation entity wirelessly, wherein the transportation statusmessage comprises a fifth set of message information elements includinginformation related to the current location.
 10. The apparatus of claim9, wherein the first set of message information elements in thetransportation request message further comprises at least one of a typeof transport device requested, a number of users, a validity time forthe transportation request message, a maximum travel time or requireddestination arrival time, or a combination thereof.
 11. The apparatus ofclaim 9, wherein the fourth set of message information elements in thetransportation status request message further includes the identifierfor the user device, a query for information related to an estimate ofarrival to the requested destination, and wherein the fifth set ofmessage information elements in the transportation status messagefurther includes the estimate of arrival to destination.
 12. Theapparatus of claim 11, wherein the estimate of arrival to destinationcomprises one or more of estimated time of arrival to destination andestimated number of stops to destination, and wherein the fifth set ofmessage information elements in the transportation status messagefurther includes a destination of a transport vehicle nearest therequested destination.
 13. The apparatus of claim 9, wherein the atleast one processor is further configured to: transmit a transportregistration message to the transportation entity, wherein the transportregistration message includes a payment method to be charged fortransport; and receive a first acknowledgement message for thetransportation registration message from the transportation entity basedon the transport registration message, wherein the transportationrequest message is broadcasted to the transportation entity based on thefirst acknowledgement message.
 14. The apparatus of claim 13, whereinthe at least one processor is further configured to: transmit aderegistration message to the transportation entity, wherein thederegistration message completes a purchase based on the payment method.15. The apparatus of claim 9, wherein the at least one processor isfurther configured to: broadcast a transportation complete requestmessage to the transportation entity wirelessly, wherein thetransportation complete request message comprises a sixth set of messageinformation elements including the identifier for the user device, and arequest to disembark; receive a transportation complete acknowledgementmessage broadcasted by the transportation entity wirelessly, wherein thetransportation complete acknowledgement message comprises a seventh setof message information elements including an estimate of arrival todestination and a confirmation of the request to disembark; and receivea transportation complete response message broadcasted by thetransportation entity wirelessly, wherein the transportation completeresponse message comprises an eighth set of message information elementsincluding the identifier for the user device, and including at least oneof an ingress location, an egress location, a fare and a request toprovide periodic signals to validate that the user device has exited atransport vehicle.
 16. A method of wireless communication at atransportation entity, comprising: receiving a transportation requestmessage broadcasted by a user device wirelessly, wherein thetransportation request message comprises a first set of messageinformation elements including an identifier for the user device and arequested destination; broadcasting a transportation response message tothe user device wirelessly, wherein the transportation response messagecomprises a second set of message information elements includingacceptance or rejection of the transportation request message; receivinga transportation confirm message from the user device wirelessly inresponse to the acceptance in the transportation response message,wherein the transportation confirm message comprises a third set ofmessage information elements including the identifier for the userdevice; receiving a transportation status request message broadcasted bythe user device wirelessly, wherein the transportation status requestmessage comprises a fourth set of message information elements includinga query for information related to a current location; and broadcastinga transportation status message to the user device wirelessly, whereinthe transportation status message comprises a fifth set of messageinformation elements including information related to the currentlocation.
 17. The method of claim 16, wherein the first set of messageinformation elements in the transportation request message furthercomprises at least one of a type of transport device requested, a numberof users, a validity time for the transportation request message, amaximum travel time or required destination arrival time, or acombination thereof.
 18. The method of claim 16, wherein thetransportation request message, the transportation response message, andthe transportation confirm message are dedicated messages in aDevice-to-Device (D2D) communication link, comprising one or more of adedicated short-range communication (DSRC), a cellularVehicle-to-Everything (C-V2X) communication, or a 5G New Radio (NR)communication.
 19. The method of claim 16, wherein the fourth set ofmessage information elements in the transportation status requestmessage further includes the identifier for the user device, a query forinformation related to an estimate of arrival to the requesteddestination, and wherein the fifth set of message information elementsin the transportation status message further includes the estimate ofarrival to destination.
 20. The method of claim 19, wherein the estimateof arrival to destination comprises one or more of estimated time ofarrival to destination and estimated number of stops to destination. 21.The method of claim 19, wherein the fifth set of message informationelements in the transportation status message further includes adestination of a transport vehicle nearest the requested destination.22. The method of claim 16, further comprising: receiving atransportation complete request message broadcasted by the user devicewirelessly, wherein the transportation complete request messagecomprises a sixth set of message information elements including theidentifier for the user device, and a request to disembark; andbroadcasting a transportation complete acknowledgement message to theuser device wirelessly, wherein the transportation completeacknowledgement message comprises a seventh set of message informationelements including an estimate of arrival to destination and aconfirmation of the request to disembark.
 23. The method of claim 22,further comprising: broadcasting a transportation complete responsemessage to the user device wirelessly, wherein the transportationcomplete response message comprises an eighth set of message informationelements including the identifier for the user device, and including atleast one of an ingress location, an egress location, a fare and arequest to provide periodic signals to validate that the user device hasexited a transport vehicle.
 24. An apparatus for wireless communicationat a transportation entity, comprising: a memory; and at least oneprocessor coupled to the memory and configured to: receive atransportation request message broadcasted by a user device wirelessly,wherein the transportation request message comprises a first set ofmessage information elements including an identifier for the user deviceand a requested destination; broadcast a transportation response messageto the user device wirelessly, wherein the transportation responsemessage comprises a second set of message information elements includingacceptance or rejection of the transportation request message; receive atransportation confirm message from the user device wirelessly inresponse to the acceptance in the transportation response message,wherein the transportation confirm message comprises a third set ofmessage information elements including the identifier for the userdevice; receive a transportation status request message broadcasted bythe user device wirelessly, wherein the transportation status requestmessage comprises a fourth set of message information elements includinga query for information related to a current location; and broadcast atransportation status message to the user device wirelessly, wherein thetransportation status message comprises a fifth set of messageinformation elements including information related to the currentlocation.
 25. The apparatus of claim 24, wherein the first set ofmessage information elements in the transportation request messagefurther comprises at least one of a type of transport device requested,a number of users, a validity time for the transportation requestmessage, a maximum travel time or required destination arrival time, ora combination thereof.
 26. The apparatus of claim 24, wherein thetransportation request message, the transportation response message, andthe transportation confirm message are dedicated messages in aDevice-to-Device (D2D) communication link, comprising one or more of adedicated short-range communication (DSRC), a cellularVehicle-to-Everything (C-V2X) communication, or a 5G New Radio (NR)communication.
 27. The apparatus of claim 24, wherein the fourth set ofmessage information elements in the transportation status requestmessage further includes the identifier for the user device, a query forinformation related to an estimate of arrival to the requesteddestination, and wherein the fifth set of message information elementsin the transportation status message further includes the estimate ofarrival to destination.
 28. The apparatus of claim 27, wherein theestimate of arrival to destination comprises one or more of estimatedtime of arrival to destination and estimated number of stops todestination.
 29. The apparatus of claim 27, wherein the fifth set ofmessage information elements in the transportation status messagefurther includes a destination of a transport vehicle nearest therequested destination.
 30. The apparatus of claim 24, wherein the atleast one processor is further configured to: receive a transportationcomplete request message broadcasted by the user device wirelessly,wherein the transportation complete request message comprises a sixthset of message information elements including the identifier for theuser device, and a request to disembark; broadcast a transportationcomplete acknowledgement message to the user device wirelessly, whereinthe transportation complete acknowledgement message comprises a seventhset of message information elements including an estimate of arrival todestination and a confirmation of the request to disembark; andbroadcast a transportation complete response message to the user devicewirelessly, wherein the transportation complete response messagecomprises an eighth set of message information elements including theidentifier for the user device, and including at least one of an ingresslocation, an egress location, a fare and a request to provide periodicsignals to validate that the user device has exited a transport vehicle.